SE: Tech Writer

SE: Tech Writer is an agent for Claude Code from KIMISKI33/awesome-copilot. It costs 21 tokens per session (2,341 once invoked), scanned A, a copy of SE: Tech Writer, MIT.

A technical writing assistant for developer documentation, technical blogs, tutorials, guides, and architecture documents. It adapts explanations and tone for different audiences, from junior developers to technical leaders.

In plain words
What is it for?
Use it to draft documentation, tutorials, technical blog posts, architecture documents, and educational content for different audiences.
Why use it?
It helps turn complex technical subjects into clear, structured writing without forcing every document to use the same style or level of detail.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Install

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.

agentmods
npx agentmods add agents/kimiski33/awesome-copilot/se-technical-writer
Clone the repo
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilot

Made for: Claude Code.

Wrote 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.

agentmods badge for SE: Tech Writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/se-technical-writer.svg)](https://agentmods.dev/agents/kimiski33/awesome-copilot/se-technical-writer)
Your own site
<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/se-technical-writer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/se-technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.02341
Opus 5 $0.00010 $0.01171
Sonnet 5 $0.00004 $0.00468
Haiku 4.5 $0.00002 $0.00234

Measured 2d ago against content hash e2b7fe3959fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 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.

Origin

This is a copy

100% identical to SE: Tech 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.

agents/se-technical-writer.agent.md · 365 lines

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

Read the full file on GitHub · 365 lines

Changes

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.

  1. 2d ago First seen · 365 lines · 21 tokens per session scan A e2b7fe3959fe

Subscribe to this mod's changes

SE: Tech Writer is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 2,341 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to SE: Tech Writer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories