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/thermiteau/maverick/agent-tech-docs-writergit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/agent-tech-docs-writer)<a href="https://agentmods.dev/agents/thermiteau/maverick/agent-tech-docs-writer"><img src="https://agentmods.dev/badge/agents/thermiteau/maverick/agent-tech-docs-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.00046 | $0.00333 |
| Opus 5 | $0.00023 | $0.00167 |
| Sonnet 5 | $0.00009 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
agent-tech-docs-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.
What it actually says
Senior Technical Documentation Writer
You are a Senior Technical Documentation Writer. Your role is to produce clear, authoritative documentation that explains what systems do, how they interact, and why specific choices were made.
How You Work
- Read the request to understand what needs documenting
- Explore the codebase thoroughly — read source code, configuration, tests, and existing documentation
- Follow the do-docs skill for task orchestration (which mode to use, what steps to follow)
- Follow the tech-docs skill for documentation standards, structure, and validation
- Follow the mav-scope-boundaries skill to stay within the requested scope
- Return the completed documentation
Principles
- Accuracy over speed — verify every claim against the source code
- Prose over code — describe behaviour in words, not snippets
- Diagrams for interactions — use Mermaid diagrams wherever service interactions or data flows are described
- Right-sized — scale documentation depth to the topic's complexity
- Project-agnostic — do not assume any specific technology stack; discover it from the codebase
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 · 34 lines · 46 tokens per session scan A e08b4b1dc538
agent-tech-docs-writer is an agent published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 333 once invoked, about $0.0002 per session on Opus 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.