Borrowing it
Nothing to install: this file belongs to Andes-Software-Solutions/Andes.Extensions.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/Andes-Software-Solutions/Andes.Extensions.AI/main/.claude/agents/se-technical-writer.mdgit clone --depth 1 https://github.com/Andes-Software-Solutions/Andes.Extensions.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/andes-software-solutions/andes.extensions.ai/se-technical-writer)<a href="https://agentmods.dev/agents/andes-software-solutions/andes.extensions.ai/se-technical-writer"><img src="https://agentmods.dev/badge/agents/andes-software-solutions/andes.extensions.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.00048 | $0.02442 |
| Opus 5 | $0.00024 | $0.01221 |
| Sonnet 5 | $0.00010 | $0.00488 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
se-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 8d 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
91% identical to SE: Tech Writer — 82 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 — 433 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.
Output location: Write project documentation as Markdown files under the repository's docs/ directory (create it if it does not exist). Use clear, kebab-case file names (e.g. docs/payment-processing.md). Lead with why before how.
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
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.
- 8d ago First seen · 433 lines · 48 tokens per session scan A 5cc0ef289c2b
se-technical-writer is an agent published in the GitHub repository Andes-Software-Solutions/Andes.Extensions.AI (9 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 2,442 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to SE: Tech Writer, differing in 82 lines, and is treated as a copy.
Other agents, from other repositories
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
MAF Cross-Framework Migration Agent
Use when migrating an app FROM Semantic Kernel (C#) TO Microsoft Agent Framework (MAF) — a cross-framework port, NOT a MAF version upgrade. Inventories SK usage, classifies every construct (🌉 bridge / 🔁 rewrite / 🏗 re-architect), writes a plan, scaffolds a NEW MAF project beside the original (non-destructive), and…
dotnet-perf-full-probe
Benchmark-only instrument for dotnet-performance. Answers a stated C#-navigation question with BOTH tool families available at once — this repo's dotnet-toolkit MCP tools AND Read/Grep/Glob/Bash — under the plugin's shipped default guard state (advisory, not suspended, not forced-block). Plays a real, unrestricted…
csharp-developer
Expert C# developer specializing in modern .NET development, ASP.NET Core, and cloud-native applications. Masters C# 12 features, Blazor, and cross-platform development with emphasis on performance and clean architecture.
fluent-validation
Cria validators FluentValidation consistentes para DTOs do — regras, mensagens em português e integração com ASP.NET Core.