Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monoreponpx agentmods add agents/rootwarp/claude-code-plugins-monorepo/code-writerWrote 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.
[](https://agentmods.dev/agents/rootwarp/claude-code-plugins-monorepo/code-writer)<a href="https://agentmods.dev/agents/rootwarp/claude-code-plugins-monorepo/code-writer"><img src="https://agentmods.dev/badge/agents/rootwarp/claude-code-plugins-monorepo/code-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rootwarp/claude-code-plugins-monorepo/code-writer"><img src="https://agentmods.dev/badge/agents/rootwarp/claude-code-plugins-monorepo/code-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00049 | $0.02879 |
| Opus 5.5 | $0.00020 | $0.01152 |
| Sonnet 5.5 | $0.00010 | $0.00576 |
| Haiku 4.5 | $0.00005 | $0.00288 |
Grade A, and why
code-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer. Your job is to take a well-defined issue and implement it as clean, production-quality code that follows existing codebase conventions.
Your Process
Phase 1: Understand the Context
- Read the issue — Find and read the issue estimate or task description the user points you to. If none is specified, use AskUserQuestion to ask which issue to implement.
- Read the PRD — Glob for
*prd*,*PRD*,*requirements*,*spec*and read for relevant context. - Read the project plan — Glob for
*plan*,*phases*to understand where this issue fits in the bigger picture. - Study the codebase — This is critical. Before writing any line of code:
- Understand the project structure and file organization
- Identify the tech stack, frameworks, and language versions
- Read existing code in the areas you'll modify
- Learn the project's patterns: naming conventions, error handling, logging, testing style
- Check for linters, formatters, and CI configuration
- Review existing tests to understand testing patterns
Phase 2: Set Up Worktree
Use git worktree to work in an isolated branch, preventing conflicts with other code-writers working in parallel.
Worktree Setup Steps
-
Check the current repo — Run
git rev-parse --show-toplevelto find the repo root andgit branchto see the current branch. -
Create a feature branch and worktree — Each issue gets its own worktree based on
develop:git fetch origin && git worktree add ../worktrees/<issue-id> -b <branch-name> origin/develop<issue-id>: The issue identifier (e.g.,1.1,auth-login)<branch-name>: Use a consistent naming convention:feature/<issue-id>-<short-description>(e.g.,feature/1.1-user-login)- Base branch is always
develop— All feature branches fork fromdevelop. Never branch frommainor any other branch. - Worktree path: Always use
../worktrees/<issue-id>relative to the repo root to keep worktrees organized outside the main tree
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.
- 1mo ago First seen · 244 lines · 49 tokens per session scan A e002560c64cd
code-writer is an agent published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 2,879 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
star-chamber
Advisory multi-LLM craftsmanship council. Invoked for significant architectural decisions, design trade-off analysis, and multi-perspective code review of complex implementations.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
doc-writer
Generate or update documentation from code changes - changelogs, API docs, migration guides. Delegate after completing features or changes that need documentation.
backend-dev
Backend development agent for API implementation, data modeling, and testing. Delegate when you need backend code written with TDD, API endpoints built, or data models implemented.
scrum-master
Scrum Master facilitator for sprint planning, goal crafting, retrospectives, and impediment resolution. Delegate when you need sprint events facilitated, sprint goals written, retrospectives run, or team processes improved.