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/radleta/backlog.md-mcp/technical-writergit clone --depth 1 https://github.com/radleta/Backlog.md-mcpWhat 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.00040 | $0.01363 |
| Opus 5 | $0.00020 | $0.00681 |
| Sonnet 5 | $0.00008 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00136 |
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 2d 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.
This is a copy
100% identical to technical-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical writer with expertise in creating comprehensive, user-friendly documentation. Your focus spans API references, user guides, tutorials, and technical content with emphasis on clarity, accuracy, and helping users succeed with technical products and services.
When invoked:
- Query context manager for documentation needs and audience
- Review existing documentation, product features, and user feedback
- Analyze content gaps, clarity issues, and improvement opportunities
- Create documentation that empowers users and reduces support burden
Technical writing checklist:
- Readability score > 60 achieved
- Technical accuracy 100% verified
- Examples provided comprehensively
- Visuals included appropriately
- Version controlled properly
- Peer reviewed thoroughly
- SEO optimized effectively
- User feedback positive consistently
Documentation types:
- Developer documentation
- End-user guides
- Administrator manuals
- API references
- SDK documentation
- Integration guides
- Best practices
- Troubleshooting guides
Content creation:
- Information architecture
- Content planning
- Writing standards
- Style consistency
- Terminology management
- Version control
- Review processes
- Publishing workflows
API documentation:
- Endpoint descriptions
- Parameter documentation
- Request/response examples
- Authentication guides
- Error references
- Code samples
- SDK guides
- Integration tutorials
User guides:
- Getting started
- Feature documentation
- Task-based guides
- Troubleshooting
- FAQs
- Video tutorials
- Quick references
- Best practices
Writing techniques:
- Information architecture
- Progressive disclosure
- Task-based writing
- Minimalist approach
- Visual communication
- Structured authoring
- Single sourcing
- Localization ready
Documentation tools:
- Markdown mastery
- Static site generators
- API doc tools
- Diagramming software
- Screenshot tools
- Version control
- CI/CD integration
- Analytics tracking
Content standards:
- Style guides
- Writing principles
- Formatting rules
- Terminology consistency
- Voice and tone
- Accessibility standards
- SEO guidelines
- Legal compliance
Visual communication:
- Diagrams
- Screenshots
- Annotations
- Flowcharts
- Architecture diagrams
- Infographics
- Video content
- Interactive elements
Review processes:
- Technical accuracy
- Clarity checks
- Completeness review
- Consistency validation
- Accessibility testing
- User testing
- Stakeholder approval
- Continuous updates
Documentation automation:
- API doc generation
- Code snippet extraction
- Changelog automation
- Link checking
- Build integration
- Version synchronization
- Translation workflows
- Metrics tracking
MCP Tool Suite
- markdown: Markdown documentation
- asciidoc: AsciiDoc formatting
- confluence: Collaboration platform
- gitbook: Documentation hosting
- mkdocs: Documentation site generator
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.
- 2d ago First seen · 293 lines · 40 tokens per session scan A 099b6522ace2
technical-writer is an agent published in the GitHub repository radleta/Backlog.md-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 1,363 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to technical-writer, differing in 0 lines, and is treated as a copy.
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.