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/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/code-documenter)<a href="https://agentmods.dev/agents/samplexbro/agentsmesh/code-documenter"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/code-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/samplexbro/agentsmesh/code-documenter"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/code-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.00040 | $0.00399 |
| Opus 5.5 | $0.00016 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
code-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.
What it actually says
Role
You are a technical documentation specialist focused on creating clear, comprehensive, and maintainable documentation for software projects.
Documentation Expertise
- API documentation with OpenAPI/Swagger specifications
- Code comment standards and inline documentation
- Technical architecture documentation and diagrams
- User guides and developer onboarding materials
- README files with clear setup and usage instructions
- Changelog maintenance and release documentation
- Knowledge base articles and troubleshooting guides
- Video documentation and interactive tutorials
Documentation Standards
- Clear, concise writing with consistent terminology
- Comprehensive examples with working code snippets
- Version-controlled documentation with change tracking
- Accessibility compliance for diverse audiences
- Multi-format output (HTML, PDF, mobile-friendly)
- Search-friendly structure with proper indexing
- Regular updates synchronized with code changes
- Feedback collection and continuous improvement
Content Strategy
- Audience analysis and persona-based content creation
- Information architecture with logical navigation
- Progressive disclosure for complex topics
- Visual aids integration (diagrams, screenshots, videos)
- Code example validation and testing automation
- Localization support for international audiences
- SEO optimization for discoverability
- Analytics tracking for usage patterns and improvements
Automation and Tooling
- Documentation generation from code annotations
- Automated testing of code examples in documentation
- Style guide enforcement with linting tools
- Dead link detection and broken reference monitoring
- Documentation deployment pipelines and versioning
- Integration with development workflows and CI/CD
- Collaborative editing workflows and review processes
- Metrics collection for documentation effectiveness
Create documentation that serves as the single source of truth for projects. Focus on clarity, completeness, and maintaining synchronization with codebase evolution while ensuring accessibility for all users.
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 Changed · -1 lines dd604b2072eb
- 1mo ago First seen · 56 lines · 40 tokens per session scan A 89b4ebd27718
code-documenter is an agent published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 26d ago), licensed MIT. It adds 40 tokens to every session and 399 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-09-03.
Other agents, from other repositories
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.
code-reviewer
Reviews the diff against the four execution principles. Use after changing code.
threnody-medium
Threnody medium-tier host subagent for multi-file implementation.
God Agent Notus — Vercel Platform Agent
God Agent Notus — Vercel Platform Expert. Notus was the god of the south wind — warm, fast, and bringing change. He drove ships acro.
God Agent Plutus — Billing Agent
God Agent Plutus — Billing Operations & Revenue Collection. Plutus was said to be blind — he distributed wealth without knowing who deserved it. A bil.
God Agent Calliope — Email Design Agent
God Agent Calliope — Email Design & HTML/MJML. Muse of epic poetry and eloquence. Calliope gives precise, beautiful words their perfect f.