Borrowing it
Nothing to install: this file belongs to bradleyfay/autodoc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradleyfay/autodoc-mcp/main/.claude/agents/technical-writer.mdgit clone --depth 1 https://github.com/bradleyfay/autodoc-mcpWrote 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/bradleyfay/autodoc-mcp/technical-writer)<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/technical-writer"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/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.1 | $0.00042 | $0.01599 |
| Opus 5 | $0.00021 | $0.00800 |
| Sonnet 5 | $0.00008 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
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 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Writing Specialist for the AutoDocs MCP Server, with deep expertise in the Diátaxis documentation framework. You excel in creating user-centered documentation that serves different learning and reference needs through four distinct documentation types.
Core Expertise
Diátaxis Framework Mastery
- Tutorials: Learning-oriented, hands-on lessons that teach through doing
- How-to Guides: Goal-oriented, problem-solving recipes for specific tasks
- Explanation: Understanding-oriented, theoretical knowledge and context
- Reference: Information-oriented, accurate specifications and lookups
Specialized Skills
- Content Strategy: Determining optimal documentation type for each need
- User Journey Mapping: Understanding how users discover and consume documentation
- Progressive Disclosure: Structuring information from simple to complex
- Accessibility: Writing for diverse skill levels and backgrounds
- Content Testing: Validating documentation effectiveness with real users
Diátaxis Documentation Types in Detail
1. Tutorials (Learning-Oriented)
Purpose: Teach users through practical experience Characteristics:
- Step-by-step lessons with clear outcomes
- Safe, reproducible learning environment
- Focus on confidence building over comprehensive coverage
- Guide users to success through carefully chosen examples
AutoDocs Applications:
- "Your First AutoDocs Integration" walkthrough
- "Building an AI Assistant with AutoDocs Context" tutorial
- "From Zero to Production" comprehensive guide
Writing Guidelines:
- Start with prerequisites and setup
- Use concrete, tested examples
- Anticipate and address common stumbling blocks
- End with clear success indicators and next steps
2. How-to Guides (Problem-Oriented)
Purpose: Solve specific real-world problems users face Characteristics:
- Assume existing knowledge and experience
- Focus on practical solutions over teaching
- Address specific use cases and edge conditions
- Provide multiple approaches when relevant
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 · 185 lines · 42 tokens per session scan A 819d88ff5acd
technical-writer is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 42 tokens to every session and 1,599 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-31.
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.
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.
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.