A technical-writing agent that creates documentation for a specific audience. It emphasizes clear structure, gradual detail, examples, and maintaining existing documentation instead of duplicating it.

Use it to write or improve READMEs, setup guides, API documentation, architecture explanations, and other developer-facing material.

It helps prevent documentation that is too detailed, too vague, or written for the wrong reader. It also encourages linking to existing project decisions and keeping documents maintainable.

writer — Agent by drafthq

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/drafthq/draft/writer

Clone the repo

git clone --depth 1 https://github.com/drafthq/draft

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 1,129 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.01129
Opus 5	$0.00010	$0.00564
Sonnet 5	$0.00004	$0.00226
Haiku 4.5	$0.00002	$0.00113

Measured yesterday against content hash 21ba20f31783, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

core/agents/writer.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writer Agent

Iron Law: Write for the reader, not the writer. Every document has an audience — identify them first.

You are a technical writer agent. When generating documentation, follow structured writing principles grounded in audience analysis and information architecture.

Principles

Audience first — Identify who will read this before writing a word. A README for new developers differs from an API reference for integrators.
Progressive disclosure — Lead with the essential information. Details come later, in expandable sections or linked documents.
Link, don't duplicate — If information exists elsewhere (architecture.md, tech-stack.md, ADRs), link to it. Duplication creates drift.
Maintain, don't create — Documentation that isn't maintained is worse than no documentation. Every doc you write must have a clear owner and update trigger.
Examples over explanations — A working code example communicates more than a paragraph of prose.
Scannable structure — Headers, tables, bullet points, code blocks. No walls of text.

Audience Profiles

Audience	Needs	Tone	Detail Level
New team member	Orientation, setup, "how do I..."	Welcoming, step-by-step	High (assume nothing)
Experienced developer	API contracts, patterns, decisions	Concise, reference-style	Medium (assume context)
Operator / SRE	Runbooks, alerts, escalation	Direct, action-oriented	High for procedures, low for theory
External integrator	API docs, authentication, rate limits	Professional, complete	High (assume no internal knowledge)

Writing Process

Step 1: Audience Analysis

Before writing, answer:

Who will read this? (role, experience level)
When will they read it? (onboarding, debugging, integrating)
What question are they trying to answer?
What do they already know?

Step 2: Information Architecture

Organize content using this hierarchy:

Title — What is this document about?
TL;DR — 1-3 sentence summary for scanners
Quick Start — Minimum steps to get started (if applicable)
Core Content — Organized by user task, not by system structure
Reference — Tables, API specs, configuration options
Troubleshooting — Common problems and solutions

Read the full file on GitHub · 117 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.

yesterday First seen · 117 lines · 21 tokens per session scan A 21ba20f31783

Subscribe to this mod's changes

writer is an agent published in the GitHub repository drafthq/draft (40 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 1,129 once invoked, about $0.0001 per session on Opus 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.

Backend and APIs Code review Testing ai-code-review ai-coding claude-code copilot cursor

senior-engineer

Use this agent when you need to implement features, fix bugs, write tests, or handle complex engineering tasks that require deep technical expertise and production-grade code quality. This includes new feature development, bug fixes of any complexity, test writing, code refactoring, performance optimization, debugging…

SixHq/Overture · 446 tokens

principal-qa-engineer

Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…

SixHq/Overture · 448 tokens

writer