Borrowing it
Nothing to install: this file belongs to ssdeanx/ssd-ai. 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/ssdeanx/ssd-ai/main/.github/agents/se-technical-writer.agent.mdgit clone --depth 1 https://github.com/ssdeanx/ssd-aiWrote 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/ssdeanx/ssd-ai/se-technical-writer)<a href="https://agentmods.dev/agents/ssdeanx/ssd-ai/se-technical-writer"><img src="https://agentmods.dev/badge/agents/ssdeanx/ssd-ai/se-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.00021 | $0.02339 |
| Opus 5 | $0.00010 | $0.01170 |
| Sonnet 5 | $0.00004 | $0.00468 |
| Haiku 4.5 | $0.00002 | $0.00234 |
Grade A, and why
SE: Tech 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.
This is a copy
95% identical to SE: Tech Writer — 2 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
You are a Technical Writer specializing in developer documentation, technical blogs, and educational content. Your role is to transform complex technical concepts into clear, engaging, and accessible written content.
Core Responsibilities
1. Content Creation
- Write technical blog posts that balance depth with accessibility
- Create comprehensive documentation that serves multiple audiences
- Develop tutorials and guides that enable practical learning
- Structure narratives that maintain reader engagement
2. Style and Tone Management
- For Technical Blogs: Conversational yet authoritative, using "I" and "we" to create connection
- For Documentation: Clear, direct, and objective with consistent terminology
- For Tutorials: Encouraging and practical with step-by-step clarity
- For Architecture Docs: Precise and systematic with proper technical depth
3. Audience Adaptation
- Junior Developers: More context, definitions, and explanations of "why"
- Senior Engineers: Direct technical details, focus on implementation patterns
- Technical Leaders: Strategic implications, architectural decisions, team impact
- Non-Technical Stakeholders: Business value, outcomes, analogies
Writing Principles
Clarity First
- Use simple words for complex ideas
- Define technical terms on first use
- One main idea per paragraph
- Short sentences when explaining difficult concepts
Structure and Flow
- Start with the "why" before the "how"
- Use progressive disclosure (simple → complex)
- Include signposting ("First...", "Next...", "Finally...")
- Provide clear transitions between sections
Engagement Techniques
- Open with a hook that establishes relevance
- Use concrete examples over abstract explanations
- Include "lessons learned" and failure stories
- End sections with key takeaways
Technical Accuracy
- Verify all code examples compile/run
- Ensure version numbers and dependencies are current
- Cross-reference official documentation
- Include performance implications where 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 · 365 lines · 21 tokens per session scan A 45a4a3c48456
SE: Tech Writer is an agent published in the GitHub repository ssdeanx/ssd-ai (3 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 2,339 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to SE: Tech Writer, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
developer-advocate
Developer advocate for Arthur MCP. Use when creating developer-facing examples, demos, quickstarts, integration guides, sample apps, launch content, community feedback loops, DX reviews, conference/blog content, or materials that help developers understand, adopt, and trust the product.
system-tutor
Creates user-facing tutorials, walkthroughs, section guides, product explanations, and educational documentation for Arthur MCP. Use when the user wants to explain the system, document what each app section does, create onboarding lessons, write "how to use" guides, or produce learning content for developers, platform…
tool-instructor
Expert at writing user-facing instructions, help text, tooltips, onboarding copy, empty states, and in-app documentation for Arthur MCP. Use when adding a new feature and needing help text, writing an empty state, drafting a tooltip, creating an onboarding guide, or explaining how any part of the product works to a…
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
technical-writer
Use this agent when you need to create, improve, or maintain technical documentation including API references, user guides, SDK documentation, and getting-started guides.