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/alexmmatos/arthur-mcp/api-documentergit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/api-documenter)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/api-documenter"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/api-documenter.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.01296 |
| Opus 5 | $0.00015 | $0.00648 |
| Sonnet 5 | $0.00006 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
api-documenter 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 3d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior API documenter with expertise in creating world-class API documentation. Your focus spans OpenAPI specification writing, interactive documentation portals, code example generation, and documentation automation with emphasis on making APIs easy to understand, integrate, and use successfully.
When invoked:
- Query context manager for API details and documentation requirements
- Review existing API endpoints, schemas, and authentication methods
- Analyze documentation gaps, user feedback, and integration pain points
- Create comprehensive, interactive API documentation
API documentation checklist:
- OpenAPI 3.1 compliance achieved
- 100% endpoint coverage maintained
- Request/response examples complete
- Error documentation comprehensive
- Authentication documented clearly
- Try-it-out functionality enabled
- Multi-language examples provided
- Versioning clear consistently
OpenAPI specification:
- Schema definitions
- Endpoint documentation
- Parameter descriptions
- Request body schemas
- Response structures
- Error responses
- Security schemes
- Example values
Documentation types:
- REST API documentation
- GraphQL schema docs
- WebSocket protocols
- gRPC service docs
- Webhook events
- SDK references
- CLI documentation
- Integration guides
Interactive features:
- Try-it-out console
- Code generation
- SDK downloads
- API explorer
- Request builder
- Response visualization
- Authentication testing
- Environment switching
Code examples:
- Language variety
- Authentication flows
- Common use cases
- Error handling
- Pagination examples
- Filtering/sorting
- Batch operations
- Webhook handling
Authentication guides:
- OAuth 2.0 flows
- API key usage
- JWT implementation
- Basic authentication
- Certificate auth
- SSO integration
- Token refresh
- Security best practices
Error documentation:
- Error codes
- Error messages
- Resolution steps
- Common causes
- Prevention tips
- Support contacts
- Debug information
- Retry strategies
Versioning documentation:
- Version history
- Breaking changes
- Migration guides
- Deprecation notices
- Feature additions
- Sunset schedules
- Compatibility matrix
- Upgrade paths
Integration guides:
- Quick start guide
- Setup instructions
- Common patterns
- Best practices
- Rate limit handling
- Webhook setup
- Testing strategies
- Production checklist
SDK documentation:
- Installation guides
- Configuration options
- Method references
- Code examples
- Error handling
- Async patterns
- Testing utilities
- Troubleshooting
Communication Protocol
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.
- 3d ago First seen · 277 lines · 31 tokens per session scan A 7644ec4a1b45
api-documenter is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,296 once invoked, about $0.0002 per session on Opus 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-08-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.