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 agentmods add skills/rahmanef63/si-coder-agent/sc-clerknpx skills add rahmanef63/si-coder-agent --skill sc-clerkgit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-clerk)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-clerk"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-clerk.svg" alt="Measured on agentmods" 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 | $0.00068 | $0.00649 |
| Opus 5 | $0.00034 | $0.00324 |
| Sonnet 5 | $0.00014 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
sc-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 today.
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.
What it actually says
/sc-clerk — Clerk auth (STUB)
Status: boilerplate only. Use only when a project explicitly chooses Clerk over
@convex-dev/auth.
When to use
By default /sc-all and /sc-convex use @convex-dev/auth. Use /sc-clerk only when:
- The user explicitly requests Clerk.
- An existing project already uses Clerk and is being migrated/maintained.
- You want a managed auth UI without running self-hosted JWKS.
Scope when implemented
- Read Clerk instance from
CLERK_SECRET_KEY(Backend API). - Configure allowed origins (
NEXT_PUBLIC_<app-url>+ dev origin). - Create a JWT template named
convexwith the correct issuer claim so Convex can verify. - Write
NEXT_PUBLIC_CLERK_FRONTEND_API_URL+ publishable key to project.env. - Set up Convex
auth.config.tswithproviders: [{ domain: <clerk-issuer>, applicationID: 'convex' }].
Env vars
| Var | Purpose |
|---|---|
CLERK_SECRET_KEY |
sk_test_ or sk_live_ Backend API key |
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY |
pk_test_ or pk_live_ Frontend key |
NEXT_PUBLIC_CLERK_FRONTEND_API_URL |
https://<issuer-domain> |
Suggested file layout
sc-clerk/
├── SKILL.md
└── scripts/
├── instance.js # read instance config + origins
├── set-origins.js # update allowed origins
├── jwt-template.js # create the 'convex' JWT template
└── sync-convex-auth-config.js # write auth.config.ts in project
Note on Clerk MCP
Once clerk MCP is installed (https://mcp.clerk.com/mcp), prefer it for SDK snippet generation, integration patterns, and SDK-version-specific advice. /sc-clerk handles provisioning (origins, JWT template, env setup); Clerk MCP handles code patterns.
What ships with it
1 file 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.
- today Changed · +6 lines 6cbbb65a18a8
- 5d ago First seen · 48 lines · 68 tokens per session scan A ce156d16cca3
sc-clerk is a skill published in the GitHub repository rahmanef63/si-coder-agent (14 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 649 once invoked, about $0.0003 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
convex-http-actions
External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation.
convex-migrations
Schema migration strategies for evolving applications including adding new fields, backfilling data, removing deprecated fields, index migrations, and zero-downtime migration patterns.
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
convex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
convex-security-audit
Deep security review patterns for authorization logic, data access boundaries, action isolation, rate limiting, and protecting sensitive operations.
avoid-feature-creep
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.