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/oxygen-fragment/claude-modularWrote 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/oxygen-fragment/claude-modular/api-docs)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/api-docs"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/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/oxygen-fragment/claude-modular/api-docs"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/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.00000 | $0.00605 |
| Opus 5.5 | $0.00000 | $0.00242 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
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.
What it actually says
API Documentation Command
2. **Schema Generation**
- Generate OpenAPI/Swagger specifications
- Create GraphQL schema documentation
- Extract data models and types
- Document validation rules and constraints
3. **Example Generation**
- Create realistic request/response examples
- Generate code samples in multiple languages
- Include error handling examples
- Add authentication flow examples
4. **Interactive Documentation**
- Set up interactive API explorer
- Configure try-it-out functionality
- Add mock server integration
- Include testing playground
5. **Documentation Enhancement**
- Add comprehensive descriptions
- Include usage guidelines and best practices
- Document rate limiting and quotas
- Add troubleshooting guides
6. **Publishing and Maintenance**
- Generate static documentation sites
- Set up automatic updates from code
- Configure version management
- Enable team collaboration features
# Generated documentation:
# - OpenAPI/Swagger specs
# - Interactive API explorer
# - Code examples
# - Authentication guides
```
```bash
# Generate docs for specific API version
/docs:api-docs --version=v2
# Version-specific documentation:
# - v2 API endpoints
# - Migration guides
# - Deprecation notices
# - Version comparison
```
```bash
# Generate docs with custom examples
/docs:api-docs --examples=production-data
# Enhanced documentation:
# - Real-world examples
# - Production use cases
# - Performance guidelines
# - Best practices
```
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 · 98 lines · 0 tokens per session scan A c8d3234c4365
api-docs is a command published in the GitHub repository oxygen-fragment/claude-modular (285 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 605 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-30.
Other commands, from other repositories
api-smoke.skeleton
Description: This section is filled by Bootstrap from manifest data. Required manifest fields: project.description, stack.primary, environments Example output.
contrato-api
Diseñar contratos de API, webhooks e integraciones con manejo de errores y reintentos.
planificar-tecnico
Generar blueprint técnico desde una especificación Gherkin.
qbackenddev
Autonomous backend/infrastructure development session driven by a work file.
f5-design
Generate design documents and specifications (D1-D4).
f5-backend
Backend development commands.