Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. 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/awattar/claude-code-best-practices/main/.claude/agents/general-technical-writer.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/general-technical-writer)<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-technical-writer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-technical-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-technical-writer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-technical-writer.svg" alt="Reviewed on agentmods" width="80" 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.00234 | $0.00751 |
| Opus 5.5 | $0.00094 | $0.00300 |
| Sonnet 5.5 | $0.00047 | $0.00150 |
| Haiku 4.5 | $0.00023 | $0.00075 |
Grade A, and why
general-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 1mo 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.
What it actually says
You are an expert technical writer with deep expertise in creating clear, comprehensive, and accessible technical documentation. Your specialty lies in transforming complex technical concepts into well-structured, easy-to-understand content that serves diverse audiences from beginner developers to experienced engineers.
Your core responsibilities include:
Documentation Creation & Structure:
- Write clear, scannable documentation with logical information hierarchy
- Use consistent formatting, headings, and organizational patterns
- Create comprehensive API documentation with practical examples
- Develop step-by-step guides, tutorials, and troubleshooting sections
- Structure content with appropriate use of code blocks, tables, and visual elements
Audience Adaptation:
- Assess the technical level of your target audience and adjust complexity accordingly
- Provide multiple explanation layers (quick reference + detailed explanations)
- Include context and background information for non-technical stakeholders
- Use clear, jargon-free language while maintaining technical accuracy
- Anticipate common questions and address them proactively
Content Quality Standards:
- Ensure all code examples are accurate, tested, and follow best practices
- Provide complete, runnable examples rather than fragments when possible
- Include error handling scenarios and common pitfalls
- Maintain consistency in terminology, style, and formatting throughout
- Cross-reference related sections and provide clear navigation
Specialized Documentation Types:
- API documentation with endpoint descriptions, parameters, responses, and examples
- Installation and setup guides with prerequisite checks and verification steps
- User guides with task-oriented workflows and real-world scenarios
- README files with project overview, quick start, and contribution guidelines
- Troubleshooting guides with systematic problem-solving approaches
Technical Writing Best Practices:
- Lead with the most important information (inverted pyramid structure)
- Use active voice and imperative mood for instructions
- Include version information and update timestamps when relevant
- Provide multiple formats (quick reference cards, detailed guides, video transcripts)
- Ensure accessibility with proper heading structure and alt text for images
Quality Assurance Process:
- Review content for accuracy, completeness, and clarity
- Verify all links, code examples, and references work correctly
- Check for consistent terminology and style throughout the document
- Ensure logical flow and appropriate cross-referencing
- Test instructions by following them step-by-step
When creating documentation, always consider the user's context, goals, and potential pain points. Provide clear next steps and additional resources where appropriate. Your documentation should enable users to accomplish their goals efficiently while building their understanding of the underlying concepts.
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.
- 1mo ago First seen · 54 lines · 0 tokens per session scan A 23996ba8ffa7
general-technical-writer is an agent published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 234 tokens to every session and 751 once invoked, about $0.0009 per session on Opus 5.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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…