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.
git clone --depth 1 https://github.com/JosiahSiegel/claude-plugin-marketplaceWrote 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/plugins/josiahsiegel/claude-plugin-marketplace/clerk-auth-master)<a href="https://agentmods.dev/plugins/josiahsiegel/claude-plugin-marketplace/clerk-auth-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/clerk-auth-master/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/plugins/josiahsiegel/claude-plugin-marketplace/clerk-auth-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/clerk-auth-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
clerk-auth-master 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 2mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "clerk-auth-master",
"version": "1.0.2",
"description": "Comprehensive Clerk authentication expertise across Next.js, React, JavaScript, Node/Express/Fastify, Go, Ruby, Python, Java, .NET, PHP, sessions, JWT templates, organizations, middleware/proxy, API auth, webhooks, dev/prod environments, JWT clock skew and nbf/iat/exp failures, and production security. PROACTIVELY activate for: (1) any Clerk auth task, (2) sign-in/sign-up/user profile flows, (3) protected routes and middleware/proxy setup, (4) auth()/currentUser()/clerkClient usage, (5) cross-origin Bearer tokens, (6) webhook verification and user sync, (7) dev/prod instance separation, DNS, redirects, custom domains, CORS, (8) organizations, roles, permissions, MFA, passkeys, bot protection, (9) token-not-active-yet/token-expired/clockSkewInMs/WSL2/Docker Desktop time drift, and deployment gotchas. Provides: framework-specific implementation patterns, multi-language backend guidance, clock-skew diagnostics, and security reviews.",
"author": {
"name": "Josiah Siegel"
},
"license": "MIT",
"keywords": [
"clerk",
"clerk-auth",
"authentication",
"auth",
"identity",
"signin",
"signup",
"user-management",
"sessions",
"jwt",
"jwt-templates",
"nextjs",
"nextjs-auth",
"proxy-ts",
"middleware",
"app-router",
"react",
"javascript",
"typescript",
"node",
"express",
"fastify",
"go",
"ruby",
"rails",
"python",
"fastapi",
"django",
"flask",
"java",
"spring",
"dotnet",
"csharp",
"aspnet",
"php",
"laravel",
"api-auth",
"bearer-token",
"webhooks",
"svix",
"organizations",
"roles",
"permissions",
"mfa",
"passkeys",
"bot-protection",
"oauth",
"production",
"deployment",
"custom-domain",
"dev-instance",
"prod-instance",
"security",
What it installs
The manifest is a name and a version. 4 skills, 1 agent travel with it, and installing the plugin installs all of them — 871 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 81 lines scan A 07be71247649
clerk-auth-master is a plugin published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (59 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
clerk-auth-master compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| clerk-auth-masterJosiahSiegel/claude-plugin-marketplace | Plugin | 59 | 4mo ago | MIT | A | — | Claude Code |
| app-builderadobe/skills | Plugin | 319 | yesterday | Apache-2.0 | A | — | Claude Code |
| rails-consultantthoughtbot/rails-consultant | Plugin | 28 | 7d ago | MIT | A | — | Claude Code |
| load-testerrohitg00/awesome-claude-code-toolkit | Plugin | 2.8k | 5mo ago | Apache-2.0 | A | — | Claude Code |
| rabbitmqadminfprochazka/claude-code-plugins | Plugin | 14 | 28d ago | MIT | A | — | Claude Code |
| jpm-payments-skillsjpmorgan-payments/pdp-skills | Plugin | 8 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| authhimself65/auth-spec | Plugin | 41 | 28d ago | none | A | — | Claude Code |