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 JosiahSiegel/claude-plugin-marketplace --skill clerk-frontend-sdksgit 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/skills/josiahsiegel/claude-plugin-marketplace/clerk-frontend-sdks)<a href="https://agentmods.dev/skills/josiahsiegel/claude-plugin-marketplace/clerk-frontend-sdks"><img src="https://agentmods.dev/badge/skills/josiahsiegel/claude-plugin-marketplace/clerk-frontend-sdks/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/josiahsiegel/claude-plugin-marketplace/clerk-frontend-sdks"><img src="https://agentmods.dev/badge/skills/josiahsiegel/claude-plugin-marketplace/clerk-frontend-sdks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00132 | $0.01905 |
| Opus 5 | $0.00066 | $0.00953 |
| Sonnet 5 | $0.00026 | $0.00381 |
| Haiku 4.5 | $0.00013 | $0.00191 |
Grade A, and why
clerk-frontend-sdks 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 12d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clerk Frontend SDKs
Overview
Use this skill for client-side Clerk integration across React and other frontend frameworks. The main job is choosing the correct framework SDK, wiring provider context, selecting prebuilt UI vs custom flows, handling environment-specific redirects, and avoiding the mistake of treating client auth state as server authorization.
SDK Selection
Prefer the dedicated framework SDK when one exists:
| App type | Preferred package/pattern |
|---|---|
| Next.js | @clerk/nextjs |
| React app without a stronger integration | @clerk/react |
| React Router framework | Clerk React Router SDK/patterns |
| TanStack React Start | Clerk TanStack integration |
| Astro | Clerk Astro integration |
| Nuxt/Vue | Clerk Nuxt/Vue integration |
| Expo/mobile | Clerk Expo/mobile integration |
| Plain JavaScript/non-React | ClerkJS |
Selecting the wrong SDK causes routing, SSR, hydration, and token propagation bugs. Check the package already installed before adding another package.
Provider and Environment Setup
Wire the frontend provider near the root of the app. The provider should receive a publishable key or use the framework SDK's environment-variable convention. Never pass a secret key, webhook signing secret, or Backend API credential to browser code.
Use development and production Clerk instances deliberately. Auth bugs often come from mixing a development publishable key with production domains, production redirect URLs, production Backend API secrets, or production webhooks.
Provider-level options and environment variables must align with Clerk Dashboard URLs:
- Sign-in route/path.
- Sign-up route/path.
- After-sign-in and after-sign-up fallback/force redirects.
- Allowed origins/domains.
- OAuth redirect and callback settings for production providers.
- Custom domain/proxy settings when used.
Prebuilt Components vs Custom Flows
Prefer Clerk prebuilt components for standard auth UX:
- Sign in and sign up pages or modals.
- User button and account management.
- User profile and organization profile.
- Organization switcher and organization list flows.
- Multi-session account switching when supported by the chosen UI.
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.
- 12d ago First seen · 183 lines · 132 tokens per session scan A e75308b987a7
clerk-frontend-sdks is a skill published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (54 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session and 1,905 once invoked, about $0.0007 per session on Opus 5. 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
ui-toolkit/web
Reference skill for Zoom Video SDK UI Toolkit. Use after routing to a web video workflow when you want prebuilt React UI instead of building a fully custom Video SDK interface.
zoom-meeting-sdk-web-component-view
Zoom Meeting SDK Web - Component View. Embeddable Zoom meeting components with Promise-based API for flexible integration. Ideal for React/Vue/Angular apps and custom layouts. Uses ZoomMtgEmbedded with async/await patterns and embeddable UI containers.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
tanstack-form
Headless, performant, and type-safe form state management for TS/JS, React, Vue, Angular, Solid, Lit, and Svelte.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
web-development
Use when users need to implement, integrate, debug, build, deploy, or validate a Web frontend after the product direction is already clear, especially for React, Vue, Vite, browser flows, or CloudBase Web integration.