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.
git clone --depth 1 https://github.com/FlorianBruniaux/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/commands/florianbruniaux/claude-code-plugins/plan-start)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/plan-start"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/plan-start/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/commands/florianbruniaux/claude-code-plugins/plan-start"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/plan-start.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.00039 | $0.01615 |
| Opus 5.5 | $0.00016 | $0.00646 |
| Sonnet 5.5 | $0.00008 | $0.00323 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
plan-start 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Start — 5-Phase Planning
Analyze the request and produce a complete implementation plan through structured phases. No code is written. Every significant decision is recorded. Run /clear after this command before running /plan-validate.
Phase 1: PRD & Design Analysis
Step 1.1 — PRD Analysis
Skip if no PRD exists (refactor, infra change, bug fix).
Read all PRD files and docs/INFORMATION_ARCHITECTURE.md if present. Scan the codebase to understand current implementation status.
Surface findings in 3 buckets:
Missing requirements — acceptance criteria that are absent or incomplete Ambiguous requirements — items with multiple valid interpretations Compliance concerns — security, data privacy, API contract implications
For each finding: present options with concrete pros/cons. Discuss with user. Record every decision in the plan file under a ## Decisions section before moving on. Do not proceed past unresolved ambiguities.
Step 1.2 — Design Analysis
Skip if no UI changes are in scope.
Read: DESIGN_SYSTEM.md, existing UX ADRs, CLAUDE.md UX rules.
Produce specs for:
- Screen inventory: new/modified screens, route placement, component reuse audit
- State catalog: empty, loading, populated, error, and partial states for every interactive element
- Interaction specs: user flows (happy path + alternates), focus/keyboard behavior
- Animation specs: map each interaction to existing keyframes or specify new ones, include
prefers-reduced-motionfallbacks - Responsive behavior: breakpoints, web/mobile divergence decisions
- Accessibility: WAI-ARIA pattern selection, live regions, error visibility
Create Design ADRs for significant UX decisions (choice of interaction pattern, new animation convention, platform divergence). Record minor layout choices directly in the plan file.
Phase 2: Technical Analysis
Spawn 1-2 Explore agents for targeted codebase research. Run them in the background via Task tool.
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 · 181 lines · 39 tokens per session scan A d44183a5018c
plan-start is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,615 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-09-04.
Other commands, from other repositories
team
Virtual eng team orchestrator. Runs a goal end-to-end through the whole team — strategy → plan → build → QA → ship — conducted by the engineering-manager, delegating to every specialist. One entry point that connects /ceo-review, /eng-review, /qa, and /ship.
content-start
Content production session start command. Gives the daily content session a structured start, shows pending work, and sets priorities.
proposal
Client proposal command. Builds a professional client proposal from project summaries. Valid for 30 days.
dashboard
Daily statistics panel. Presents task, audit, event, and performance data as a unified table.
onboard
Project onboarding command. For adapting to a new project quickly and thoroughly.
start
Badi session start command. Runs new-project onboarding or a daily kickoff.