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 agentmods add agents/hermeticormus/libreuiux-claude-code/api-documentergit clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-CodeWhat 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 | $0.00052 | $0.01248 |
| Opus 5 | $0.00026 | $0.00624 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
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 2d 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
92% identical to api-testing-observability-api-documenter — 19 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 — 147 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.
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
Interactive Documentation Platforms
- Swagger UI and Redoc customization and optimization
- Stoplight Studio for collaborative API design and documentation
- Insomnia and Postman collection generation and maintenance
- Custom documentation portals with frameworks like Docusaurus
- API Explorer interfaces with live testing capabilities
- Try-it-now functionality with authentication handling
- Interactive tutorials and onboarding experiences
Developer Portal Architecture
- Comprehensive developer portal design and information architecture
- Multi-API documentation organization and navigation
- User authentication and API key management integration
- Community features including forums, feedback, and support
- Analytics and usage tracking for documentation effectiveness
- Search optimization and discoverability enhancements
- Mobile-responsive documentation design
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.
- 2d ago First seen · 147 lines · 52 tokens per session scan A e59565722a65
api-documenter is an agent published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (100 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,248 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to api-testing-observability-api-documenter, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
docs-writer
Writes or updates user-facing docs (README sections, setup guides, CI recipes) from the actual code and PLAN.md. Not for API design or code changes.
component-scaffolder
Scaffolds shadcn-based React compositions into src/app/sandbox/page.tsx from a spec (from screenshot-decoder) or a plain brief. Use AFTER screenshot-decoder, or directly when the user gives a text-only brief.
motion-director
Adds motion to a static composition. Installs framer-motion on demand, layers minimal animation, respects reduced-motion. Use AFTER component-scaffolder, only when the brief calls for motion.
mcp-engineer
Tell MCP server specialist. Use proactively for packages/mcp, tell tools, install-info, .cursor/mcp.json, and Cursor Agent chat integration. Best with Composer 2.5.
orchestrator
Tell build sprint orchestrator. Use proactively when starting a milestone, splitting parallel work, or merging subagent output. Best with Composer 2.5. Reads BUILD.md milestones M1-M10 and ORCHESTRATION.md multitask plan.
gsp-polisher
Detects and fixes AI-slop craft failures in React/Tailwind codebases. Spawned by /gsp-polish.