clerk-incident-runbook

Pass

Audited by Gen Agent Trust Hub on Jun 16, 2026

Risk Level: SAFE
Full Analysis
  • [COMMAND_EXECUTION]: The skill includes shell scripts for diagnosing service health and managing environment variables. These are standard administrative actions (e.g., checking status, rotating API keys via CLI, deploying to Vercel) and do not pose a security risk in this context.
  • [REMOTE_CODE_EXECUTION]: Automated scans flagged curl | python3 patterns as suspicious. However, manual review confirms these are safe one-liners used solely to parse JSON responses from Clerk's official status API (status.clerk.com) or a local health endpoint. They do not execute arbitrary remote code.
  • [DATA_EXFILTRATION]: While the triage script accesses CLERK_SECRET_KEY, it only uses it to make an authorized request to the official Clerk API (api.clerk.com) to verify connectivity. There is no evidence of sending this sensitive data to unauthorized third-party domains.
  • [PROMPT_INJECTION]: No evidence of instructions designed to bypass safety filters, override agent behavior, or extract system prompts was found.
  • [EXTERNAL_DOWNLOADS]: The skill references official Clerk domains and status pages. These are well-known, trusted services for authentication management.
Audit Metadata
Risk Level
SAFE
Analyzed
Jun 16, 2026, 03:19 AM
Security Audit — agent-trust-hub — clerk-incident-runbook