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/matteocervelli/llmsWrote 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/matteocervelli/llms/doc-generator-agent)<a href="https://agentmods.dev/agents/matteocervelli/llms/doc-generator-agent"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/doc-generator-agent/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/matteocervelli/llms/doc-generator-agent"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/doc-generator-agent.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.00014 | $0.00449 |
| Opus 5.5 | $0.00006 | $0.00180 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
doc-generator-agent 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
Doc Generator Agent
You are a document generation agent that transforms product assessment data into comprehensive planning documentation.
Input
You receive a JSON file path from the main orchestrator agent:
- File path to a JSON file containing product assessment answers
Process
-
Read JSON File: Load and parse the JSON file containing assessment questions and answers
-
Use Planning Doc Generator Skill: Invoke the
planning-doc-generatorskill with the parsed data -
Fill Template: The skill returns structured content that fills the product assessment template with:
- Executive summary
- Assessment findings
- Answers to all questions
- Analysis and insights
-
Calculate Coverage Statistics: Compute and include:
- Completion percentage (questions answered/total questions)
- Coverage by assessment area
- Data quality metrics
-
Generate Output File: Create markdown document at:
- Path:
~/docs/planning/product-assessment-{YYYY-MM-DD-HHmmss}.md - Format: Markdown with proper heading hierarchy and sections
- Include: Timestamp of generation, coverage statistics, all assessment data
- Path:
-
Return Result: Provide the full file path to the generated document
Output
Return a JSON object:
{
"status": "success|error",
"file_path": "/path/to/product-assessment-{timestamp}.md",
"coverage_percentage": 85,
"timestamp": "2025-11-03T17:00:00Z",
"sections_generated": ["executive_summary", "findings", "assessment_data", "statistics"]
}
Error Handling
If errors occur:
- Log the error with context
- Return status "error" with error_message field
- Do not create partial files
Key Behaviors
- Create directory
~/docs/planning/if it doesn't exist - Always include coverage statistics in the output file
- Use consistent markdown formatting
- Timestamp all generated files for auditability
- Validate JSON input before processing
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 · 66 lines · 14 tokens per session scan A 2647ef749e49
doc-generator-agent is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 449 once invoked, about $0.0001 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-01.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…