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.
npx skills add melodic-software/claude-code-plugins --skill write-for-agentsgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/skills/melodic-software/claude-code-plugins/write-for-agents)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/write-for-agents"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/write-for-agents/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/skills/melodic-software/claude-code-plugins/write-for-agents"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/write-for-agents.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.00155 | $0.02681 |
| Opus 5.5 | $0.00062 | $0.01072 |
| Sonnet 5.5 | $0.00031 | $0.00536 |
| Haiku 4.5 | $0.00015 | $0.00268 |
Grade A, and why
write-for-agents 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write For Agents
Why this skill exists
The docs-hygiene siblings are audit-shaped: they find problems in docs that already exist. This
skill is the write-side complement. It fires while the doc is being written, so the problems the
audits catch are not created in the first place. Its scope is any markdown an agent will consume;
the auto-read surfaces (CLAUDE.md scopes, .claude/rules, auto-memory, and their kin) are the
high-value core because their cost recurs every session. Read
reference/agent-doc-surfaces.md when you need to know
whether, when, and how much of a target file the harness actually loads. Write differently for
an always-loaded surface than for an on-demand one.
Budget both loads
Every line you write spends two budgets, and cutting one can overspend the other:
- Context load. Tokens the agent pays, every session for always-loaded surfaces. Governed marketplace-wide by plugin-philosophy's Instruction economy: an instruction earns its place with observed-stumble evidence, or it goes.
- Cognitive load. Attention the human maintainer pays. The maintainer keeps the map of the doc set in their head: they must be able to hold where things live. Ten tiny fragment files can be cheaper for the agent and ruinous for the human; one 500-line file the reverse. When the two budgets conflict, say which one you spent and why.
Fewer words spends less of both, and the brevity rules that are universal apply here too: no more
words than the meaning needs, no filler, hedging, intensifiers, expletive openings, or restatement
of an adjacent line; active voice; one idea per sentence; a factual register with nothing sold.
/writing:be-concise owns those rules when the writing plugin is installed; without it, apply
them from this paragraph. Take those rules and no more of that doctrine: its human-only rules do
not transfer. A bottom-line-first opening, headings written to be skimmed, bullet lists for
scanning, and bounded bold all serve a person moving down a page fast, and an agent reading a rule
needs the rule stated where it applies, not staged for a skim.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago Changed fbd8dca106a1
- 12d ago Changed · +1 lines f2caf5df785e
- 14d ago Changed · +28 tokens per session 615a496e0242
- 16d ago Changed f0d425ec78e4
- 17d ago Changed · +18 lines 841726a5d758
- 18d ago Changed · +1 lines 09573ffc938c
- 21d ago Changed · -63 tokens per session f750708992d1
- 26d ago Changed · +21 lines 57be946b7048
- 1mo ago Changed · -10 tokens per session a2a5ca5eed0b
- 1mo ago First seen · 135 lines · 200 tokens per session scan A fce6238813c2
write-for-agents is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 2,681 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
validate-before-process
For input validation: check format and constraints before processing, fail fast with clear errors, defensive parsing.