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/codeverbojan/claude-code-kickstartWrote 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/commands/codeverbojan/claude-code-kickstart/api-route)<a href="https://agentmods.dev/commands/codeverbojan/claude-code-kickstart/api-route"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/api-route/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/commands/codeverbojan/claude-code-kickstart/api-route"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/api-route.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.00015 | $0.00280 |
| Opus 5.5 | $0.00006 | $0.00112 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
api-route 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 1mo 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.
What it actually says
API Route Playbook
1. Design
- HTTP method + path
- Request schema (what fields, what types, what's required)
- Response schema (success + error shapes)
- Auth requirement (public, authenticated, admin-only)
2. Build
Follow this order in the handler:
- Auth check — verify session/token, check role
- CSRF check — on mutations (POST, PUT, DELETE)
- Input validation — parse with schema (Zod, joi, Pydantic, etc.)
- Business logic — parameterized queries only, never interpolate input
- Response — proper status codes, consistent error shape
3. Security Checklist
- Auth on the endpoint
- Input validated server-side
- No secrets in response
- Parameterized DB queries
- Rate limiting considered
- Error messages don't leak internals
4. Verify
- Run type-checker
- Run linter
- Write/run tests for: happy path, validation error, auth failure, not found
- Consider using the
security-revieweragent for a deep audit.
$ARGUMENTS
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.
- 1mo ago First seen · 37 lines · 15 tokens per session scan A f94a0dc00207
api-route is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 280 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
toh-connect
Connect app to Supabase backend with schema and RLS policies.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
setup
Interactive auth setup wizard. Choose provider, configure OAuth, email, generate schema, create UI components — all in one command.
amby.clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.
amby.plan
Produce the technical implementation plan (the HOW) from an approved spec and UI.
amby.review
Review an artifact from another role's perspective — findings by stable ID, advisory only.