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/dev-api)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/dev-api"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-api/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/dev-api"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-api.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.00346 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
dev-api 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 Agent
Create or document REST, GraphQL, or tRPC endpoints, with a versioning strategy.
Endpoint or API to process
$ARGUMENTS
Goal
Develop well-structured, documented, and testable APIs following the TDD approach.
Use the dev-api skill for the detailed methodology (RESTful structure, validation, OpenAPI documentation, tests, tRPC type-safe routers, and API versioning). For GraphQL schema/resolver depth (DataLoader, N+1 prevention, Apollo pairing), the dedicated dev-graphql skill triggers automatically.
TDD prerequisites
Mandatory creation order:
- Define the API contract (OpenAPI spec/types)
- Write the integration tests (RED)
- Implement the handler (GREEN)
- Refactor if necessary (REFACTOR)
- Document (Swagger/OpenAPI)
Expected output
Endpoint specification
- Method and path
- Description
- Parameters and body
- Possible responses (success and errors)
Implementation code
- Route with validation
- Handler
- Integration tests
Related agents
| Agent | When to use it |
|---|---|
/doc:doc-api-spec |
Generate OpenAPI/Swagger spec |
/dev:dev-tdd |
Test the endpoints |
/qa:qa-security |
API security audit |
/qa:qa-review |
API code review |
IMPORTANT: An API is a contract. Document before implementing.
IMPORTANT: Version the API (/v1/, /v2/) to avoid breaking changes.
YOU MUST validate all user inputs.
NEVER expose sensitive data in API responses.
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 · 54 lines · 0 tokens per session scan A 2c1b68cd7e15
dev-api 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 346 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-08-31.
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.