Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ashish7802/awesome-api-skills --skill clerkgit clone --depth 1 https://github.com/ashish7802/awesome-api-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ashish7802/awesome-api-skills/clerk)<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/clerk"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/clerk/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/clerk"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/clerk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00588 |
| Opus 5 | $0.00000 | $0.00294 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
clerk scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clerk API Skill
Quick Start
Clerk provides comprehensive authentication UIs and a powerful backend API. Install the specific SDK for your framework (e.g., @clerk/nextjs).
npm install @clerk/nextjs
Common Workflows
Webhook Synchronization
Do not continuously query Clerk for user data. Instead, configure Clerk Webhooks (user.created, user.updated) to push data to your primary database (Neon, Supabase). Rely on your local database for JOINs.
Production Patterns
JWT Verification
For microservices (Go, Python) communicating with a Clerk-secured frontend, extract the Bearer token and verify the JWT signature using Clerk's public JWKS endpoint. Do not rely solely on the frontend session state.
Error Recovery
Handle webhook delivery failures gracefully. Clerk webhooks include built-in Svix retry logic. Your webhook handler must be idempotent (e.g., using INSERT ... ON CONFLICT DO UPDATE).
Security Notes
Always verify the Svix signature on incoming webhooks to ensure the payload actually originated from Clerk. Never trust unverified JWTs in backend routes.
Performance Considerations
Clerk heavily optimizes the Auth object on the Edge. Use auth() or getAuth() in server components to avoid unnecessary network round trips when extracting the userId.
Testing Guidance
For E2E testing (Playwright/Cypress), utilize Clerk's dedicated Testing Tokens to bypass the UI flow and programmatically authenticate test runners without hitting rate limits or triggering fraud detection.
Troubleshooting
If auth() returns null in a Next.js App Router setup, ensure your middleware.ts is configured correctly and the route isn't accidentally excluded from the clerkMiddleware matcher.
References
Related Skills
Why use this skill
Use this when your agent works with clerk — structured patterns beat pasted docs and prevent common hallucinations.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 61 lines · 0 tokens per session scan A 815e53f4311c
clerk is a skill published in the GitHub repository ashish7802/awesome-api-skills (13 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 588 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
composio
Build AI agents and apps with Composio - access 200+ external tools with Tool Router or direct execution.
analyzing-api-gateway-access-logs
Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
testing-integration
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
presentation
Turn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.