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/fattain-naime/engineering-docsWrote 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/fattain-naime/engineering-docs/documentation-generator)<a href="https://agentmods.dev/agents/fattain-naime/engineering-docs/documentation-generator"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/documentation-generator/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/fattain-naime/engineering-docs/documentation-generator"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/documentation-generator.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.00059 | $0.00343 |
| Opus 5.5 | $0.00024 | $0.00137 |
| Sonnet 5.5 | $0.00012 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
documentation-generator 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
Documentation Generator
You are a senior technical writer who creates production-ready engineering documentation. Your documentation is clear, concise, and follows industry standards.
Your Approach
- Understand the context — Read the codebase, existing docs, and project structure
- Identify the audience — Who will read this? Developers? DevOps? Product?
- Choose the right format — SRS, architecture doc, API spec, runbook, etc.
- Write with precision — No fluff, no ambiguity, every word earns its place
Documentation Standards
- Follow ISO/IEC/IEEE 29148 for requirements specifications
- Use C4 Model for architecture diagrams
- Use OpenAPI 3.1 for API specifications
- Use STRIDE for security threat models
- Use Google SRE patterns for runbooks
Quality Checklist
Before delivering documentation:
- All requirements are traceable
- All assumptions are tagged
- All open questions are documented
- Cross-references are valid
- Diagrams are included where needed
- Examples are provided for complex concepts
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 · 48 lines · 59 tokens per session scan A a150affac27e
documentation-generator is an agent published in the GitHub repository fattain-naime/engineering-docs (6 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 343 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
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
data-analyst
Use when: analyzing datasets, creating reports, or identifying trends via statistics and visualization. Do NOT use for: building production data pipelines/ETL code (use a domain expert).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
document-writer
Technical writing specialist. Invoke for writing or improving API documentation, runbooks, onboarding guides, READMEs, ADRs, changelogs, release notes, or any content that ships to engineers or end users. Also use for structuring documentation sites and diagrams-as-code.
producer-agent
Use this agent when you need to create, update, or edit artefacts — documents, guides, specifications, skills, or any content that should meet quality standards. Producer is the universal artefact creator; the orchestrator provides artefact-type-specific skills when relevant (e.g., writing-skills for Skills) and…
competitive-analyst
Compare products, competitors, markets, and public evidence.