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.
git clone --depth 1 https://github.com/niksacdev/engineering-team-agentsWrote 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/niksacdev/engineering-team-agents/technical-writer)<a href="https://agentmods.dev/agents/niksacdev/engineering-team-agents/technical-writer"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/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/niksacdev/engineering-team-agents/technical-writer"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/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.00000 | $0.01653 |
| Opus 5.5 | $0.00000 | $0.00661 |
| Sonnet 5.5 | $0.00000 | $0.00331 |
| Haiku 4.5 | $0.00000 | $0.00165 |
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 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.
This is a copy
83% identical to SE: Tech Writer — 127 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
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.
- 1mo ago First seen · 260 lines · 0 tokens per session scan A 1dae76216ee1
technical-writer is an agent published in the GitHub repository niksacdev/engineering-team-agents (49 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,653 tokens. A static security scan graded it A with 0 findings. It is 83% identical to SE: Tech Writer, differing in 127 lines, and is treated as a copy.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
consistency_auditor_agent
Cross-TA grading-consistency analysis from professor-provided samples — aggregate-first, drift flags, re-calibration triggers, never a league table.
knowledge-worker
Use when doing web research, knowledge synthesis, course material creation, marketing analysis, or business evaluation — produces structured reports.