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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/doc-api-spec)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/doc-api-spec"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/doc-api-spec/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/christopherlouet/claude-base/doc-api-spec"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/doc-api-spec.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.00000 | $0.00330 |
| Opus 5.5 | $0.00000 | $0.00132 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
doc-api-spec 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
Agent DOC-API-SPEC
Generate an OpenAPI/Swagger specification for an API.
Context
$ARGUMENTS
Goal
Explore the API code, identify routes and models, and generate a complete OpenAPI 3.0 specification with schemas, authentication and examples.
Workflow
- Explore existing routes and controllers
- Identify data models and DTOs
- Generate the OpenAPI 3.0 structure (info, servers, paths, components)
- Document each endpoint (parameters, body, responses, errors)
- Define authentication schemas (JWT, API Key, OAuth2)
- Standardize error responses
- Validate the spec with redocly lint
Expected output
openapi.yaml file
- Complete specification with paths, schemas, security
Documented endpoints
| Method | Path | Description |
|---|
Checklist
- All endpoints documented
- Schemas for all models
- Examples for each response
- Authentication documented
- Standardized error codes
Related agents
| Agent | When to use it |
|---|---|
/dev:dev-api |
Create or modify the API |
/doc:doc-generate |
General documentation |
/dev:dev-tdd |
Test endpoints |
/qa:qa-security |
Check API security |
IMPORTANT: API documentation must be synchronized with the code - use generators if possible.
YOU MUST document all possible error codes.
NEVER forget examples - they make integration easier for developers.
Think hard about API ergonomics before documenting.
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 · 56 lines · 0 tokens per session scan A 109d171eba09
doc-api-spec is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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-09-03.
Other commands, from other repositories
deps-update
Audit and update dependencies safely.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
handoff
Write a session handoff document for continuity.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.