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 besimple-oss/broccoli --skill implement-from-plangit clone --depth 1 https://github.com/besimple-oss/broccoliWrote 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/besimple-oss/broccoli/implement-from-plan)<a href="https://agentmods.dev/skills/besimple-oss/broccoli/implement-from-plan"><img src="https://agentmods.dev/badge/skills/besimple-oss/broccoli/implement-from-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/besimple-oss/broccoli/implement-from-plan"><img src="https://agentmods.dev/badge/skills/besimple-oss/broccoli/implement-from-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.00060 | $0.00402 |
| Opus 5.5 | $0.00024 | $0.00161 |
| Sonnet 5.5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
implement-from-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 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.
What it actually says
Implement From Plan (step-by-step)
Input: a plan doc path (for example: plan/my-feature.md).
Preconditions (stop if missing)
- Confirm you are in the intended repo:
git rev-parse --show-toplevel - Confirm the plan doc exists:
test -f <plan-doc-path> - Confirm the working tree is clean:
git status --porcelainis empty - Ensure
codex-progress.logis gitignored and not tracked:- Add
codex-progress.logto.gitignoreif missing. - If it is tracked:
git rm --cached codex-progress.log(keep the file locally).
- Add
Workflow
- Record a base commit for later review:
BASE_SHA=$(git rev-parse HEAD) - When running this skill with Codex, use model
gpt-5.4unless the caller explicitly overrides the model. - Open
references/prompts/step-auto-mixed.mdand follow it using the plan doc path.- Important: it includes a one-time tooling discovery + dependency install + "Tooling config" phase; do that once and reuse it for every step.
- For C/C++ repositories, extend the prompt's tooling discovery to identify the repo-native build/test/lint path before Step 1. Check for
CMakeLists.txt,compile_commands.json,meson.build,BUILD/WORKSPACE,Makefile, and repo docs. Reuse the canonical configure/build/test/lint commands for each later step instead of rediscovering them.
What ships with it
1 file 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.
- 1mo ago First seen · 26 lines · 60 tokens per session scan A 1e87ae24afaf
implement-from-plan is a skill published in the GitHub repository besimple-oss/broccoli (283 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 402 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-30.
Other skills, from other repositories
memory-onboard
Use this skill when the user types /memory-onboard (or asks "set up memory for this repo" / "onboard this repo to memory" / "what should be in lore for this repo?"). It runs a repo-aware onboarding interview that produces DRAFT lore records grounded in concrete repo signals (README, ADRs, recent commits, deprecation…
plan-build
Use to turn a one-line brief into a phased, dependency-ordered epic of small, well-specified, deliverable tickets — covering BOTH "build me an app that does X from scratch" (greenfield) and "change/extend/redesign an existing app X" (brownfield, when a target repo is supplied). Clarify genuine ambiguity first, draft…
spec-author
Use to turn a brief into a structured product SPEC — a set of testable CLAUSES, each exactly one statement, tagged requirement / non-goal / decision — that a human edits and freezes before it feeds the decompose engine. Clarify genuine load-bearing ambiguity first, then draft, making the brief's quality requirements…
design-system
Use when a ticket needs a systematic token + component foundation for a frontend — the three-layer token architecture (primitive → semantic → component), W3C DTCG design-token files, theming and dark mode, component specs with full state coverage, or a recommendation for which design system a product should have.…
adversarial-reviewer
Use when you want a genuinely critical review of recent changes — before merging a PR, after a sprint, or when you suspect the review is being too agreeable. Forces perspective shifts through three hostile reviewer personas (Saboteur, New Hire, Security Auditor) that play concurrent, crash, retry and malicious-input…
brand
Use to establish or audit a product's brand so the factory's output looks intentional, not template — when a ticket asks to "create a brand", "define the design system / visual identity / palette / typography", or when delivered UI looks generic and needs a deliberate direction. Detects existing brand and extends it…