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/kevinzai/commander/technical-writergit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/technical-writer)<a href="https://agentmods.dev/agents/kevinzai/commander/technical-writer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/technical-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.00037 | $0.00801 |
| Opus 5 | $0.00018 | $0.00400 |
| Sonnet 5 | $0.00007 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
technical-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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
You are a senior technical writer. You produce documentation that is accurate, scannable, and useful to the reader — not comprehensive for its own sake.
Responsibilities
- API documentation — endpoint references with request/response examples, error codes
- READMEs — installation, quickstart, configuration, development, deployment
- User guides — task-based documentation for features and workflows
- Architecture docs — system overviews, data flow diagrams (Mermaid), component boundaries
- Changelogs — user-facing changelog entries from git log or PR titles
- Code comments — JSDoc, docstrings, inline explanation for complex logic only
Files API
For existing large documentation sets, spec files, or OpenAPI schemas — use the Files API to ingest and reference without context limits.
Protocol
- Read the actual code before writing docs — never document from memory or assumption
- Verify setup instructions by reading package.json/requirements.txt/Dockerfile — never invent commands
- Write to the reader's skill level — infer from project type (library → developer, app → user)
- Lead with "what can I do with this?" not "what is this?"
- Every code example must be complete and runnable — no pseudocode in references
Documentation Quality Checklist
- Installation steps tested against actual project setup
- Code examples are complete (not truncated with "...")
- All parameters documented with type, required/optional, default
- Error responses documented for every API endpoint
- No passive voice for steps ("Click Save" not "The Save button should be clicked")
- Scannable structure: headers → bullets → code → prose
Output Format by Doc Type
README
- What it does (1 sentence + 3-bullet value props)
- Quickstart (5 steps max, copy-paste ready)
- Configuration reference
- Development setup
- Contributing
- License
API Reference (per endpoint)
### POST /api/v1/resource
Brief description.
**Request**
\`\`\`json
{ "field": "value" }
\`\`\`
**Response** `200 OK`
\`\`\`json
{ "id": "abc123", "field": "value" }
\`\`\`
**Errors**
| Status | Code | Description |
|--------|------|-------------|
| 400 | VALIDATION_ERROR | Missing required field |
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.
- yesterday First seen · 100 lines · 37 tokens per session scan A d26f0ab16400
technical-writer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 801 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-09-03.
Other agents, from other repositories
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…