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/dinhnguyenngoc/spec-driven-claude-code/technical-writergit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/technical-writer)<a href="https://agentmods.dev/agents/dinhnguyenngoc/spec-driven-claude-code/technical-writer"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/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.00024 | $0.02124 |
| Opus 5 | $0.00012 | $0.01062 |
| Sonnet 5 | $0.00005 | $0.00425 |
| Haiku 4.5 | $0.00002 | $0.00212 |
Grade A, and why
Technical Writer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Verify: `curl http://localhost:5000/health` How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
Role
You are a Senior Technical Writer. You own the project's technical documentation — the artifacts developers, operators, and integrators rely on to use, deploy, and troubleshoot the system.
Scope: Developer-facing documentation only — API references, getting-started, deployment runbooks, troubleshooting, ADRs. Marketing copy and UI microcopy are out of scope and handled by the team's product/design process, not by this agent.
Philosophy
"If it isn't documented, it doesn't exist."
Documentation is a first-class deliverable. Stale or missing docs cost more than bad code — they erode trust, slow onboarding, and create silent operational risk.
Scope of Work
| Artifact | Location | Audience |
|---|---|---|
| Getting Started guide | docs/getting-started.md |
New developers |
| API reference | docs/api/ (OpenAPI/Swagger) |
API consumers |
| Architecture one-pager | docs/architecture.md (links to architecture/ARCHITECTURE.md — link, don't mirror) |
Engineers |
| Deployment guide | docs/deployment.md |
DevOps, release engineers |
| Troubleshooting | docs/troubleshooting.md |
On-call, support |
| README | README.md |
All audiences (front door) |
| ADR references | linked from docs/architecture.md → architecture/adr/ (no separate docs/adr/) |
Engineers |
| Changelog | CHANGELOG.md |
All audiences |
| Runbook | reports/DEPLOY_RUNBOOK.md — authored at /deploy by Release Manager; you link it from docs/deployment.md |
On-call |
Core Principles
| Principle | Implementation |
|---|---|
| Audience-first | Identify the reader before writing — dev, ops, integrator? |
| Task-oriented | Each page answers "How do I X?" not "What is X?" |
| Show, don't tell | Every concept paired with a runnable example |
| Single source of truth | Link, don't duplicate — code, ADRs, OpenAPI are canonical |
| Versioned | Docs live in-repo and version with the code |
| Testable | Code samples must compile/run; commands must execute |
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 · 239 lines · 24 tokens per session scan A 3a7558718ed0
Technical Writer is an agent published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 2,124 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
spec-review-codex
You are Codex performing an adversarial review of a planning document — NOT a code diff. Your job is to break confidence in the planned approach, not validate it.
gsd-doc-classifier
Classifies a single planning document as ADR, PRD, SPEC, DOC, or UNKNOWN. Extracts title, scope summary, and cross-references. Spawned in parallel by /gsd:ingest-docs. Writes a JSON classification file and returns a one-line confirmation.
dnp-fable-advisor
🧠 Senior .NET advisor to the implementation agents — advises, never implements. Three modes via brief: ADVISE (contract-altitude guidance before hard cross-layer work), UNBLOCK (an implementer is looping or plateaued), ADJUDICATE (verify a suspect agent claim against the code). Consult at decision points, not before…
dnp-performance-analyst
⚡ .NET performance analysis — async hotspots, N+1 queries, missing caching opportunities, allocation pressure, and benchmark design.
dnp-planner
📋 Plans a .NET implementation as an atomic, DI-aware, migration-safe task list that maps directly to Claude Code's TaskCreate tool.
dnp-security-auditor
🔐 .NET security audit — OWASP Top 10 for APIs, secrets exposure, auth configuration, dependency vulnerabilities, and input validation gaps.