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 fprochazka/claude-code-plugins --skill write-plangit clone --depth 1 https://github.com/fprochazka/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/fprochazka/claude-code-plugins/write-plan)<a href="https://agentmods.dev/skills/fprochazka/claude-code-plugins/write-plan"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/write-plan/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/fprochazka/claude-code-plugins/write-plan"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/write-plan.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.00021 | $0.02836 |
| Opus 5.5 | $0.00008 | $0.01134 |
| Sonnet 5.5 | $0.00004 | $0.00567 |
| Haiku 4.5 | $0.00002 | $0.00284 |
Grade A, and why
write-plan 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 7d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write an Implementation Plan
Write a plan file for the work described below, then hand it off for execution. The plan must be shaped so that (a) the resulting git history is clean per the git-workflow rules, and (b) the implementation can be driven by one persistent implementation subagent that receives the plan file itself, not giant inlined excerpts.
This command is normally run after /sdlc:pre-plan and a design discussion, so most context should already be in hand — don't re-derive what's already been gathered or decided.
Scope
$ARGUMENTS
If the Scope is empty, use the current conversation context (e.g. a pre-plan briefing already produced in this session). If it's unclear what we're planning, ask the user before proceeding.
Step 1 — Load the git-workflow skill
Invoke the git:git-workflow skill first, and apply its rules to shape the plan around the ideal git history rather than the order code happens to get written. The concrete tie-in for this command: each step in the plan maps onto one intended atomic commit (or a small, named group), so the plan's structure already encodes the commit sequence.
Step 2 — Front-load every decision, before plan mode
Do not enter plan mode yet. Plan mode restricts what the permission system lets you run, and this phase may still need real work — subagent explorations, data checks, queries against external systems. Enter plan mode only in Step 3, when the only work left is writing.
The plan you write will be executed with minimal supervision — the user may not be at the keyboard while it runs. So the bar is not "do I know enough to start writing": it is "have I surfaced every decision the user would otherwise be asked mid-implementation". A question asked now costs one AskUserQuestion; the same question at step 7 stalls the whole run.
- Walk the intended steps and hunt for the decisions hiding inside them: user-facing naming, product behavior at edge cases, scope trade-offs, anything irreversible. Ask about all of it now (AskUserQuestion) — the goal is that the executing agent never has to stop for a decision.
- Genuine knowledge gaps in the code → fill with targeted, delegated exploration (subagents, not inline spelunking) — only for the gaps, not a fresh sweep.
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.
- 7d ago Changed 64c7b257c98d
- 25d ago Changed f12df4b203a2
- 1mo ago First seen · 102 lines · 21 tokens per session scan A 7e0c1dbd1a66
write-plan is a skill published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 2,836 once invoked, about $0.0001 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-12.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…