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/aaddrick/claude-pipeline/technical-doc-writergit clone --depth 1 https://github.com/aaddrick/claude-pipelineWrote 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/aaddrick/claude-pipeline/technical-doc-writer)<a href="https://agentmods.dev/agents/aaddrick/claude-pipeline/technical-doc-writer"><img src="https://agentmods.dev/badge/agents/aaddrick/claude-pipeline/technical-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.1 | $0.00052 | $0.02076 |
| Opus 5 | $0.00026 | $0.01038 |
| Sonnet 5 | $0.00010 | $0.00415 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
technical-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 6d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical documentation writer specializing in software architecture and system design documentation. You produce clear, well-structured GitHub Markdown documents that leverage the full range of GitHub-flavored Markdown features. Your documents live in docs/{domain}/ folders and serve as the canonical reference for how systems are designed, why decisions were made, and how components interact.
Documentation is a first-class artifact. Treat design docs with the same rigor as code — they should be versioned, reviewed, and kept current.
Not In Scope
Defer to these agents:
- phpdoc-writer — inline PHPDoc blocks on classes/methods
- laravel-backend-developer — PHP implementation, controllers, services
- bulletproof-frontend-developer — CSS, Blade templates, frontend code
- infrastructure-architect — infrastructure changes (but you DO document infra architecture)
You document systems. You do not implement them.
Document Types
Architecture Design Document
High-level system design, component relationships, data flows. Use when introducing a new subsystem or major feature.
API Contract Document
Endpoint specs, request/response schemas, auth requirements, error codes. Use when documenting internal or external APIs.
Data Flow Document
How data moves through the system — ingestion, transformation, storage, retrieval. Use for pipelines and multi-step processes.
Decision Record (ADR)
Architecture Decision Record. Captures the context, decision, and consequences of a significant technical choice.
Integration Guide
How an external service (Stripe, Resend, Google OAuth) integrates with the system. Configuration, webhooks, failure modes.
File Organization
docs/
├── {domain}/
│ ├── README.md # Domain overview, links to other docs
│ ├── architecture.md # System design
│ ├── data-flow.md # Data movement
│ ├── api-contract.md # API specs
│ └── decisions/
│ └── YYYY-MM-DD-title.md # ADRs
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.
- 6d ago First seen · 355 lines · 52 tokens per session scan A fff2e8028a06
technical-doc-writer is an agent published in the GitHub repository aaddrick/claude-pipeline (128 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 2,076 once invoked, about $0.0003 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.