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/berkcangumusisik/claude-code-practices/api-docsnpx skills add berkcangumusisik/claude-code-practices --skill api-docsgit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWhat 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.00022 | $0.00296 |
| Opus 5 | $0.00011 | $0.00148 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
api-docs 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 3d 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
Generate API Documentation
Routes directory: $1 (or auto-detect)
- Find all route definitions:
grep -rn "router\.\(get\|post\|put\|patch\|delete\)\|app\.\(get\|post\|put\|patch\|delete\)" ${1:-src/} --include="*.ts" -l
-
For each route, extract:
- Method + path
- Path parameters, query params
- Request body shape (from Zod schema, type, or interface)
- Response shape
- Auth requirements (middleware check)
- Error responses
-
Generate documentation in OpenAPI 3.0 YAML format OR a readable Markdown table - ask the user which format.
Markdown format:
### POST /api/users
Creates a new user.
**Body:** `{ name: string, email: string }`
**Response:** `{ id: string, createdAt: string }`
**Auth:** Bearer token required
- Save to
docs/api.mdoropenapi.yaml.
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.
- 3d ago First seen · 40 lines · 22 tokens per session scan A c832af7c53c9
api-docs is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 296 once invoked, about $0.0001 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-31.
Other skills, from other repositories
golden-chat
Use when testing the goldenchat golden build.
golden-epub
Use when testing the epub golden build.
golden-html-multi
Use when testing the multi-file html build.
golden-pdf
Use when testing the pdf golden build.
golden-pdf-ch
Use when testing chapter categorization.
golden-man
Use when testing the man golden build.