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/MadAppGang/claude-codeWrote 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/madappgang/claude-code/api-docs)<a href="https://agentmods.dev/commands/madappgang/claude-code/api-docs"><img src="https://agentmods.dev/badge/commands/madappgang/claude-code/api-docs/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/madappgang/claude-code/api-docs"><img src="https://agentmods.dev/badge/commands/madappgang/claude-code/api-docs.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.00018 | $0.00860 |
| Opus 5.5 | $0.00007 | $0.00344 |
| Sonnet 5.5 | $0.00004 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Provide comprehensive API documentation analysis for the Tenant Management Portal API by leveraging the api-analyst agent. Answer questions about endpoints, data structures, authentication, and usage patterns.
User Query
{{ARGS}}
Workflow
STEP 1: Parse User Query
Analyze the user's question to determine what they need:
- Endpoint information: Specific API routes, methods, parameters
- Data type clarification: TypeScript interfaces, field types, validation rules
- Authentication/Authorization: How to authenticate requests, required headers
- Error handling: Expected error responses, status codes
- Integration guidance: How to integrate with the API, example requests
- General overview: High-level API structure and available resources
STEP 2: Launch API Documentation Analyzer
Use the Task tool with subagent_type: "frontend:api-analyst" and provide a detailed prompt:
The user is asking: {{ARGS}}
Please analyze the Tenant Management Portal API documentation to answer this query.
Provide:
1. **Relevant Endpoints**: List all endpoints related to the query with HTTP methods
2. **Request Format**: Show request body/query parameters with types
3. **Response Format**: Show response structure with data types
4. **TypeScript Types**: Generate TypeScript interfaces for request/response
5. **Authentication**: Specify any auth requirements
6. **Examples**: Include example requests/responses
7. **Error Handling**: List possible error responses
8. **Usage Notes**: Any important considerations or best practices
Context:
- This is for a React + TypeScript frontend application
- We use TanStack Query for data fetching
- We need type-safe API integration
- Current mock API will be replaced with real API calls
STEP 3: Format and Present Results
After the agent returns its analysis:
- Structure the output clearly with section headers
- Include code examples in TypeScript
- Highlight important notes about authentication, validation, etc.
- Provide actionable guidance for implementation
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 · 134 lines · 18 tokens per session scan A 88e3599e6056
api-docs is a command published in the GitHub repository MadAppGang/claude-code (285 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 860 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-09-03.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…