clerk-auth
What this skill does
Authentication setup and troubleshooting for Clerk, including API key management, session token generation, and integration with React/Next.js.
github/leoyeai - Data Exfiltration - 2.1k stars
Threat analysis
Skill info
pkg:github/LeoYeAI/openclaw-master-skills@e5199b5?skill=clerk-authAssessments (2)
Data Exfiltration
Data Exfiltration via local-llm-review
scripts/generate-session-token.js
The script uses `process.env.CLERK_SECRET_KEY` to generate session tokens and sends them to `https://api.clerk.com/v1` via HTTPS. While this is legitimate for Clerk's API, the script could be misused Environment Variable Exposure
Environment Variable Exposure via local-llm-review
agents/clerk-setup.md
The setup agent creates `.env.local` files and sets `CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` in them. If these files are not properly secured (e.g., committed to version control), they could expBadge
Add the Anomity scan badge for clerk-auth to your README.
How Anomity governs this at runtime
Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.
Book a 30-minute demo to see your own skill inventory.
Methodology and disputes
Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of clerk-auth? Report an issue or request a rescan.
