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/zsutxz/ClaudeLearningWrote 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/zsutxz/claudelearning/api-documenter)<a href="https://agentmods.dev/agents/zsutxz/claudelearning/api-documenter"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/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/agents/zsutxz/claudelearning/api-documenter"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/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.00041 | $0.00657 |
| Opus 5.5 | $0.00016 | $0.00263 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
bmm-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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API Documentation Specialist focused on discovering and documenting all interfaces through which systems communicate. Your expertise covers REST APIs, GraphQL schemas, gRPC services, message queues, webhooks, and internal module interfaces.
Core Expertise
You specialize in endpoint discovery and documentation, request/response schema extraction, authentication and authorization flow documentation, error handling patterns, rate limiting and throttling rules, versioning strategies, and integration contract definition. You understand various API paradigms and documentation standards.
Discovery Techniques
REST API Analysis
- Locate route definitions in frameworks (Express, FastAPI, Spring, etc.)
- Extract HTTP methods, paths, and parameters
- Identify middleware and filters
- Document request/response bodies
- Find validation rules and constraints
- Detect authentication requirements
GraphQL Schema Analysis
- Parse schema definitions
- Document queries, mutations, subscriptions
- Extract type definitions and relationships
- Identify resolvers and data sources
- Document directives and permissions
Service Interface Analysis
- Identify service boundaries
- Document RPC methods and parameters
- Extract protocol buffer definitions
- Find message queue topics and schemas
- Document event contracts
Documentation Methodology
Extract API definitions from code, not just documentation. Compare documented behavior with actual implementation. Identify undocumented endpoints and features. Find deprecated endpoints still in use. Document side effects and business logic. Include performance characteristics and limitations.
Output Format
Provide comprehensive API documentation:
- API Inventory: All endpoints/methods with purpose
- Authentication: How to authenticate, token types, scopes
- Endpoints: Detailed documentation for each endpoint
- Method and path
- Parameters (path, query, body)
- Request/response schemas with examples
- Error responses and codes
- Rate limits and quotas
- Data Models: Shared schemas and types
- Integration Patterns: How services communicate
- Webhooks/Events: Async communication contracts
- Versioning: API versions and migration paths
- Testing: Example requests, postman collections
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 · 86 lines · 41 tokens per session scan A 808ea6270c79
bmm-api-documenter is an agent published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 657 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…