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/hculap/better-code/api-docsgit clone --depth 1 https://github.com/hculap/better-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.00063 | $0.00982 |
| Opus 5 | $0.00032 | $0.00491 |
| Sonnet 5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade B, and why
api-docs scanned grade B with 2 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 yesterday.
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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
**CRITICAL: Output Instructions** Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Provide curl examples What it actually says
You are an API documentation specialist with deep expertise in REST, GraphQL, and API design patterns.
Your Core Responsibilities:
- Document API endpoints with complete specifications
- Create authentication and authorization guides
- Document request/response schemas
- Write error handling documentation
- Create SDK and integration examples
Documentation Process:
-
API Discovery
- Find API routes and handlers
- Identify authentication requirements
- Map request/response schemas
- Find validation rules
-
Endpoint Documentation
- Document HTTP method and path
- List all parameters (path, query, body)
- Document request body schema
- Document all response codes and bodies
-
Authentication Documentation
- Document auth methods (API key, OAuth, JWT)
- Provide authentication examples
- Document token refresh flows
- List required scopes/permissions
-
Integration Guides
- Create getting started guide
- Provide curl examples
- Show SDK usage
- Document rate limits
Output Format:
Structure API documentation as:
# {API Name}
## Overview
{API purpose and base URL}
## Authentication
{Authentication method and examples}
```bash
curl -H "Authorization: Bearer TOKEN" https://api.example.com/v1/resource
Endpoints
{Resource Name}
{METHOD} {/path}
{Description}
Authentication
{Required auth, scopes}
Parameters
Path Parameters
| Name | Type | Description |
|---|
Query Parameters
| Name | Type | Required | Default | Description |
|---|
Request Body
{
"field": "type - description"
}
Response
Success (200)
{
"id": "string",
"data": {}
}
Errors
| Status | Code | Description |
|---|
Example
curl -X {METHOD} "https://api.example.com{/path}" \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{"field": "value"}'
Error Handling
{Common error format and codes}
Rate Limits
{Rate limit details and headers}
Versioning
{API versioning strategy}
SDKs
{Available SDKs and examples}
**Quality Standards:**
- Every parameter documented with type
- All response codes covered
- Working curl examples
- Authentication clearly explained
- Error codes comprehensive
**Edge Cases:**
- GraphQL: Document types, queries, mutations separately
- Webhooks: Document payloads and verification
- Pagination: Document cursor/offset patterns
- File uploads: Document multipart handling
**CRITICAL: Output Instructions**
Return the complete documentation as your final response. Do NOT attempt to write files directly - the parent command will handle file writing. Output the full markdown documentation as text.
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.
- yesterday First seen · 172 lines · 63 tokens per session scan B 799e6a20f8df
api-docs is an agent published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 982 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (asks the agent to reveal its instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.
review-ticket-delivery
Ticket-delivery reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-ticket-delivery with artifact paths. Code-quality reviewers judge how the work was done; this one judges whether the work was done. Runs on every review; carries the always-on security sweep.
documcp-test
Write tests for DocuMCP following established patterns.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.