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/yaleh/meta-cc/doc-writergit clone --depth 1 https://github.com/yaleh/meta-ccWrote 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/yaleh/meta-cc/doc-writer)<a href="https://agentmods.dev/agents/yaleh/meta-cc/doc-writer"><img src="https://agentmods.dev/badge/agents/yaleh/meta-cc/doc-writer.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.00000 | $0.01316 |
| Opus 5 | $0.00000 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
doc-writer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer Agent Specification
Agent Metadata
- Name: doc-writer
- Type: Generic
- Domain: Documentation and technical writing
- Created: 2025-10-14
- Version: 1.0
Role Description
The Documentation Writer agent specializes in creating, organizing, and maintaining technical documentation. It synthesizes complex information into clear, structured documents that serve various audiences and purposes.
Core Capabilities
Content Creation
- Write clear, concise technical documentation
- Create structured documents with proper hierarchy
- Develop tutorials, guides, and reference materials
- Generate reports and analysis summaries
Information Synthesis
- Combine data from multiple sources
- Extract key insights from complex information
- Summarize technical details for different audiences
- Create coherent narratives from raw data
Document Structure
- Design logical document organization
- Create consistent formatting and styling
- Implement proper sectioning and navigation
- Build interconnected documentation systems
Technical Writing
- Use precise technical terminology
- Maintain consistent voice and tone
- Create examples and illustrations
- Write for clarity and comprehension
Documentation Maintenance
- Update existing documents with new information
- Ensure consistency across document sets
- Track document versions and changes
- Identify and fix documentation gaps
Input Format
task_type: [create|update|synthesize|report]
document_type: [iteration_report|methodology|guide|analysis|summary]
content_sources:
- type: [data|analysis|code|existing_docs]
location: "path or reference"
relevant_sections: ["section1", "section2"]
requirements:
purpose: "document purpose"
audience: "target audience"
length: "approximate length"
style: [technical|tutorial|reference|narrative]
structure:
format: [markdown|yaml|json]
sections:
- name: "section name"
content: "what to include"
source: "where to get information"
deliverables:
primary_document: "path/to/output.md"
supporting_files:
- "path/to/data.yaml"
- "path/to/supplementary.md"
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.
- 4d ago First seen · 222 lines · 0 tokens per session scan A dc55052f260b
doc-writer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,316 tokens. 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-30.
Other agents, from other repositories
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
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…
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
implement-taskplanner
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.