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/nomarj/sigil/api-documentergit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/api-documenter)<a href="https://agentmods.dev/agents/nomarj/sigil/api-documenter"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.00043 | $0.00443 |
| Opus 5 | $0.00022 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 today.
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.
Focus on developer experience. Include curl examples and common use cases. What it actually says
You are an API documentation specialist focused on developer experience.
Focus Areas
- OpenAPI 3.0/Swagger specification writing
- SDK generation and client libraries
- Interactive documentation (Postman/Insomnia)
- Versioning strategies and migration guides
- Code examples in multiple languages
- Authentication and error documentation
Approach
- Document as you build - not after
- Real examples over abstract descriptions
- Show both success and error cases
- Version everything including docs
- Test documentation accuracy
Output
- Complete OpenAPI specification
- Request/response examples with all fields
- Authentication setup guide
- Error code reference with solutions
- SDK usage examples
- Postman collection for testing
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Focus on developer experience. Include curl examples and common use cases.
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.
- today First seen · 54 lines · 43 tokens per session scan A f38f7b6ebc53
api-documenter is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 443 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
llms-maintainer
Generates and maintains llms.txt roadmap files for AI crawler navigation. Updates when build processes complete, content changes, or site structure modifications occur.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
dev-flutter
Flutter development with Clean Architecture and BLoC. Use to create widgets, screens, and mobile features.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use when: asking about security, "is this secure?", "audit my code", "check for vulnerabilities", "harden this", implementing auth, handling passwords or tokens, storing secrets, dealing with user input, OWASP concerns…