Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjroy/vibe-garden/plugin install lore-developmentWrote 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/rjroy/vibe-garden/plan-breakdown)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/plan-breakdown"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/plan-breakdown/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/rjroy/vibe-garden/plan-breakdown"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/plan-breakdown.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.00058 | $0.00463 |
| Opus 5 | $0.00029 | $0.00231 |
| Sonnet 5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
plan-breakdown 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 9d 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.
What it actually says
Plan Breakdown
A plan describes what to build. This skill adds what's missing: how do you know each step is done?
Invoke when a plan is complex enough that explicit validation at each step matters before handing off to implement. Simple plans don't need it — implement can work from the plan directly.
Input
Invoked as /plan-breakdown <path> where <path> is a plan in .lore/work/plans/. Read the plan and any spec it references.
What to Add
For each plan step, define:
- What: concrete enough that an agent reading only this task knows what to build
- Validation: specific criteria, not "run the tests" — "the CLI outputs X when called with Y", "Playwright confirms the button triggers Z", "unit test covers the rejection path"
- Why: the requirement or goal this step satisfies, with a reference back to the source
- Files: affected files (guidance, not a constraint)
Split a step only when it bundles genuinely different concerns with different validation needs. Resist over-decomposition — the value is the validation gates, not artificial granularity.
Save the task list. The saved files are the review vehicle.
Output
Save task files to .lore/work/tasks/<plan-name>/NNN-<task-name>.md. Load ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md for the frontmatter fields. Set status: pending and include a sequence frontmatter field for ordering.
Each task file body: What, Validation, Why, Files sections.
Write the body in Markdown per the "Body Format" section of ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md. Reach for embedded inline HTML only when a visual carries meaning prose can't, such as a color-coded status badge or a diagram a reviewing agent needs at a glance.
Stop here. The user invokes /implement when ready.
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.
- 9d ago First seen · 37 lines · 58 tokens per session scan A 42cd84e25e51
plan-breakdown is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 463 once invoked, about $0.0003 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.
Other skills, from other repositories
init-rpm
Project setup and verification. First run creates rpm context for a project. Repeat runs verify that an existing rpm setup matches the latest expected layout and apply safe migrations.
backlog
Manage the rpm backlog (long-term project tasks in docs/rpm/future/tasks.org — distinct from Claude's native TaskCreate list, which is session-scoped). Add, list, review, postpone, or complete entries. TRIGGER on natural-language backlog operations — phrasings like "backlog X", "add X to backlog", "add to backlog"…
version
Report the installed rpm plugin version. Use when the user asks for the rpm version, plugin version, installed version, or wants to verify which rpm release is loaded.
recursive-spine-scaffold
Use when a repo has (or is getting) the tracking stamp and needs the rest of its spine — interviews for and stamps up to six parts, each optional: a rules codex with a moments map, an ADR directory, a CI gate skeleton, a session-memory convention, a constraints file with its sha-pinned drift gate, and the loop…
recursive-spine-digest
Use when sweeping all recursive-spine-conforming repos for tracking health — aging deferrals (oldest first), stalled milestones, in-flight by lane, assigned-but-untouched issues, and debts named in closing comments but never filed, plus seedling pollen that never transplanted (hive repos). Reports honest denominators…
recursive-spine-bootstrap
Use when installing the recursive-spine tracking convention onto a repo — interviews for modules and dialect, then stamps labels, issue/PR templates, a CLAUDE.md/AGENTS.md tracking section, and cross-project board membership. Idempotent; degrades loudly on missing gh scopes; offers (never forces) plumb-line and…