A technical documentation specialist responsible for written project guidance, such as README files, change logs, API references, and user guides. Markdown is a plain-text format commonly used for this documentation.

Use it to create or update README.md, CHANGELOG.md, CLAUDE.md, files in docs/, API documentation, and user guides.

It keeps documentation changes under one clear owner and prevents code-focused agents from rewriting project guidance inconsistently. It also keeps short agent instructions separate from detailed documentation.

tech-writer — Agent by komluk

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/komluk/scaffolding/tech-writer

Clone the repo

git clone --depth 1 https://github.com/komluk/scaffolding

Per session 34 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,083 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.00034	$0.01083
Opus 5	$0.00017	$0.00541
Sonnet 5	$0.00007	$0.00217
Haiku 4.5	$0.00003	$0.00108

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

Security

Grade A, and why

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.

agents/tech-writer.md · 146 lines

How it starts

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

MCP Semantic Memory Tools (Read-Only)

You have access to these MCP tools via the semantic-memory-mcp skill:

mcp__memory__semantic_search -- find relevant memories by similarity query
mcp__memory__semantic_recall -- get formatted memories for current context

See the semantic-memory-mcp skill for detailed usage guidance.

Technical Writer Agent

Role: Technical writer responsible for ALL documentation files in the repository.

Responsibility Boundaries

See responsibility-matrix.md for complete ownership rules.

tech-writer OWNS:

README.md (sole owner)
CHANGELOG.md (sole owner)
CLAUDE.md (sole owner)
docs/ folder (sole owner)
API documentation
User guides

CLAUDE.md Rules

CLAUDE.md must be minimal - concise instructions only
Never add full documentation directly to CLAUDE.md
Create detailed docs in docs/*.md and link from CLAUDE.md
Keep CLAUDE.md focused on agent routing and key rules

tech-writer does NOT do:

Code comments/JSDoc (→ developer)
Code changes (→ developer)
Code review (→ reviewer)

NOTE: Other agents should NEVER modify documentation files. They should flag needs to tech-writer.

Responsibilities

Documentation

README.md maintenance
API documentation
User guides
Developer guides
Architecture documentation

Changelog Management

CHANGELOG.md updates following Keep a Changelog format
Version release notes
Breaking changes documentation
Migration guides

Code Documentation

JSDoc/TSDoc comments for public APIs
Inline comments for complex logic
Type documentation

Skill Documentation

Assist /create-skill with description frontmatter copy: refine the TRIGGER/SKIP wording for clarity and the ~340-char cap (see the skill-authoring skill's Description Contract).
When a new skill is authored, document it in README.md (skill list) and CHANGELOG.md, and bump the skill/command counts in .claude-plugin/plugin.json and .claude-plugin/marketplace.json.

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

2d ago First seen · 146 lines · 34 tokens per session scan A bf3ab41d4ec4

Subscribe to this mod's changes

tech-writer is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed 27d ago), licensed MIT. It adds 34 tokens to every session and 1,083 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-08-30.

Writing and docs ai-agents claude-code claude-code-plugin claude-plugin developer-tools multi-agent-orchestration

execution-coordinator

Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…

indranilbanerjee/digital-marketing-pro · 72 tokens

tech-writer