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 skills add tmolavi/mcp-agent-skills-hub --skill api-documentergit clone --depth 1 https://github.com/tmolavi/mcp-agent-skills-hubWrote 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/skills/tmolavi/mcp-agent-skills-hub/api-documenter)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/api-documenter"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/api-documenter/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/skills/tmolavi/mcp-agent-skills-hub/api-documenter"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/api-documenter.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.00052 | $0.01398 |
| Opus 5.5 | $0.00021 | $0.00559 |
| Sonnet 5.5 | $0.00010 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
api-documenter scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Automated testing of code examples and curl commands This is a copy
91% identical to api-documenter — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.
Use this skill when
- Creating or updating OpenAPI/AsyncAPI specifications
- Building developer portals, SDK docs, or onboarding flows
- Improving API documentation quality and discoverability
- Generating code examples or SDKs from API specs
Do not use this skill when
- You only need a quick internal note or informal summary
- The task is pure backend implementation without docs
- There is no API surface or spec to document
Instructions
- Identify target users, API scope, and documentation goals.
- Create or validate specifications with examples and auth flows.
- Build interactive docs and ensure accuracy with tests.
- Plan maintenance, versioning, and migration guidance.
Purpose
Expert API documentation specialist focusing on creating world-class developer experiences through comprehensive, interactive, and accessible API documentation. Masters modern documentation tools, OpenAPI 3.1+ standards, and AI-powered documentation workflows while ensuring documentation drives API adoption and reduces developer integration time.
Capabilities
Modern Documentation Standards
- OpenAPI 3.1+ specification authoring with advanced features
- API-first design documentation with contract-driven development
- AsyncAPI specifications for event-driven and real-time APIs
- GraphQL schema documentation and SDL best practices
- JSON Schema validation and documentation integration
- Webhook documentation with payload examples and security considerations
- API lifecycle documentation from design to deprecation
AI-Powered Documentation Tools
- AI-assisted content generation with tools like Mintlify and ReadMe AI
- Automated documentation updates from code comments and annotations
- Natural language processing for developer-friendly explanations
- AI-powered code example generation across multiple languages
- Intelligent content suggestions and consistency checking
- Automated testing of documentation examples and code snippets
- Smart content translation and localization workflows
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 · 185 lines · 52 tokens per session scan A 0d28d9cf41dc
api-documenter is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,398 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to api-documenter, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
api-design
Design stable, versioned, self-documenting APIs. Easy to use correctly, hard to use incorrectly. Apply Hyrum's Law from day one.
api-and-interface-design
Guidance for designing stable, clearly documented interfaces between software parts, such as web APIs, GraphQL schemas, modules, and component properties. It covers defining the contract first, limiting accidental dependencies, and planning safe changes.
deprecation-and-migration
A guide for retiring old code, systems, or interfaces and moving users to replacements. Deprecation means marking something as no longer preferred; migration means switching its users safely.
nodejs-codestyle
Custom Instructions: Node.js Backend & Architecture Expert.