writer

writer is an agent for Claude Code from yash-gadodia/claude-init. It costs 30 tokens per session (317 once invoked), scanned A, original, MIT.

A specialist for writing software documentation and technical communications. It covers items such as READMEs, API references, changelogs, pull-request descriptions, architecture notes, and onboarding guides.

In plain words
What is it for?
Use it to document APIs, explain system structure, guide new contributors, describe releases, write migration guides, and summarize code changes for pull requests.
Why use it?
It turns code, tests, and project history into information that other developers can understand and use. It keeps explanations focused on purpose, setup, behavior, and changes.

Agent for Claude Code

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

Part of the claude-init plugin — 11 skills, 7 agents shipped together

Good fit Use it to document APIs, explain system structure, guide new contributors, describe releases, write migration guides, and summarize code changes for pull requests.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yash-gadodia/claude-init/writer
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.

Clone the repo
git clone --depth 1 https://github.com/yash-gadodia/claude-init

Made for: Claude Code.

Or install claude-init, the plugin that ships this one along with the rest of its 11 skills, 7 agents.

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 writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/yash-gadodia/claude-init/writer.svg)](https://agentmods.dev/agents/yash-gadodia/claude-init/writer)
Your own site
<a href="https://agentmods.dev/agents/yash-gadodia/claude-init/writer"><img src="https://agentmods.dev/badge/agents/yash-gadodia/claude-init/writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 317 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00030 $0.00317
Opus 5 $0.00015 $0.00159
Sonnet 5 $0.00006 $0.00063
Haiku 4.5 $0.00003 $0.00032

Measured 8d ago against content hash 61e963fbf992, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 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.

templates/agents/writer.md · 47 lines

What it actually says

You are a technical writer. You write clear, concise documentation.

Capabilities

README & Guides

  • Project READMEs with quick start, architecture overview, and contribution guidelines
  • Onboarding docs for new team members
  • Migration guides when the stack changes

API Documentation

  • Endpoint docs from route definitions
  • Request/response examples from tests or types
  • Error code references

Changelogs & Release Notes

  • Read git log between tags
  • Group by type (features, fixes, breaking changes)
  • Write user-facing descriptions (not commit messages)

PR Descriptions

  • Summarize changes from diff
  • Explain the "why" not just the "what"
  • List testing done and deployment notes

Architecture Docs

  • System diagrams (ASCII art, keep it portable)
  • Component responsibilities
  • Data flow documentation
  • Decision records (ADRs)

Style Rules

  • Write for the reader, not yourself
  • Lead with the most important information
  • Use bullet points over paragraphs
  • Include code examples for anything technical
  • No filler words, no "In order to..." — just "To..."
  • Keep sentences short. One idea per sentence.
  • Don't document what the code already says clearly
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. 8d ago First seen · 47 lines · 30 tokens per session scan A 61e963fbf992

Subscribe to this mod's changes

writer is an agent published in the GitHub repository yash-gadodia/claude-init (5 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 317 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-31.

Related

Other agents, from other repositories

software-architect

Use this agent when you need expert architectural guidance, including: designing system architectures, reviewing architectural decisions, analyzing trade-offs between different architectural approaches, planning technology migrations, evaluating scalability and performance implications, assessing technical debt, or…

patrickserrano/lacquer · 0 tokens

test-automation-engineer

Use this agent when you need expert assistance with test automation, including writing test cases, creating mock data, reviewing existing tests, debugging test failures, or identifying edge cases. This agent enforces TDD principles and maintains high testing standards. Examples.

patrickserrano/lacquer · 0 tokens

ios-monetization-strategist

Use this agent when you need expert guidance on ethical iOS app monetization strategies, revenue optimization, user trust building, or growth hacking techniques that respect user privacy. Examples: Context: The user is developing a mental wellness app and wants to create a sustainable business model without…

patrickserrano/lacquer · 0 tokens

ios-performance-optimizer

Use this agent when you need to analyze, diagnose, and optimize iOS application performance, including frame rates, battery efficiency, memory usage, and data query optimization. This agent should be engaged for performance profiling, identifying bottlenecks, implementing Swift concurrency patterns, ensuring memory…

patrickserrano/lacquer · 0 tokens

ios-elite-craftsman

Use this agent when you need world-class iOS development expertise that would impress the most discerning Apple ecosystem critics and thought leaders. This agent excels at crafting iOS applications with exceptional attention to platform conventions, performance optimization, and user delight. Perfect for architectural…

patrickserrano/lacquer · 81 tokens

ios-debugging-expert

Use this agent when you need to debug iOS/Swift issues, review code or tests for bugs, analyze crash logs, investigate performance problems, or collaborate on planning fixes for complex technical issues. This agent excels at root cause analysis and providing actionable debugging strategies.

patrickserrano/lacquer · 58 tokens