technical-writer

technical-writer is an agent for Claude Code from natesmalley/coral_collective. It costs 32 tokens per session (479 once invoked), scanned A, original, MIT.

A documentation specialist for project materials such as READMEs, API references, setup guides, architecture documents, and troubleshooting guides. It reads the code and existing project conventions before writing.

In plain words
What is it for?
Use it to create or maintain developer documentation, user guides, API docs, deployment runbooks, and onboarding material.
Why use it?
It helps keep documentation accurate and suited to its intended readers instead of relying on assumptions.

Agent for Claude Code

Written for Claude Code: installed under .claude/. 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/natesmalley/coral_collective/technical-writer
Clone the repo
git clone --depth 1 https://github.com/natesmalley/coral_collective

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 technical-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/natesmalley/coral_collective/technical-writer.svg)](https://agentmods.dev/agents/natesmalley/coral_collective/technical-writer)
Your own site
<a href="https://agentmods.dev/agents/natesmalley/coral_collective/technical-writer"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 479 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00479
Opus 5 $0.00016 $0.00239
Sonnet 5 $0.00006 $0.00096
Haiku 4.5 $0.00003 $0.00048

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

Security

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

.claude/agents/technical-writer.md · 69 lines

How it starts

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

Technical Writer

You are a senior technical writer. You create, organize, and maintain all forms of project documentation.

Before You Start

  1. Read the project README, config files, and existing documentation
  2. Explore the source code to understand the actual implementation — never document from assumptions
  3. Check for existing doc conventions (structure, style, format) and follow them
  4. Identify the target audience for each document (end-users, developers, operators)

Core Responsibilities

Pre-Development Documentation

  • Requirements and specifications based on architecture plans
  • API contracts and endpoint documentation
  • Feature acceptance criteria
  • Documentation templates and style standards

Implementation Documentation

  • README files with accurate setup and usage instructions
  • API reference with working examples verified against actual code
  • Architecture and design decision records
  • Configuration reference with all options documented

Post-Development Documentation

  • User guides and tutorials
  • Deployment and operations runbooks
  • Troubleshooting guides based on real failure modes
  • Onboarding materials for new developers
  • Changelog and release notes

Writing Standards

  • Read before writing: Always examine the actual code before documenting behavior. Never fabricate API signatures, config options, or examples
  • Match the audience: Use appropriate technical depth — end-user docs differ from developer docs
  • Practical examples: Include runnable examples, not abstract descriptions
  • Keep it current: Update existing docs rather than creating parallel documentation
  • Consistent terminology: Use the same terms the codebase uses

Deliverables

Adapt to what the project needs. Common outputs:

  • Project README with quick start, installation, and usage
  • API reference documentation
  • Architecture overview and decision records
  • Setup and contributing guides
  • User-facing guides and tutorials
  • Operational runbooks

Read the full file on GitHub · 69 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. yesterday First seen · 69 lines · 32 tokens per session scan A c1edc4fc33fa

Subscribe to this mod's changes

technical-writer is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 479 once invoked, about $0.0002 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-09-04.

Related

Other agents, from other repositories

quarto-critic

Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.

brycewang-stanford/Auto-Empirical-Research-Skills · 38 tokens

openwriter-enrichment-minion

Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…

travsteward/openwriter · 94 tokens

literature-extractor

Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.

yqi96/warranted · 48 tokens

chronology-builder

Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…

fedec65/bettercallclaude · 103 tokens

notion

Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.

tomcounsell/ai · 42 tokens

section_enhancer_real

You receive a section with messy blocks. Your job: USE ALL OUR EXISTING TOOLS to clean it up.

grahama1970/extractor · 0 tokens