Borrowing it
Nothing to install: this file belongs to vdaubry/bottega. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vdaubry/bottega/main/.claude/commands/planification.mdgit clone --depth 1 https://github.com/vdaubry/bottegaWrote 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/vdaubry/bottega/planification)<a href="https://agentmods.dev/commands/vdaubry/bottega/planification"><img src="https://agentmods.dev/badge/commands/vdaubry/bottega/planification/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/vdaubry/bottega/planification"><img src="https://agentmods.dev/badge/commands/vdaubry/bottega/planification.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.00020 | $0.01272 |
| Opus 5.5 | $0.00008 | $0.00509 |
| Sonnet 5.5 | $0.00004 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade B, and why
planification scanned grade B with 1 finding 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 24d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Explicit instruction: "Do NOT write any files, run any scripts, or ask user questions. Only explore How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a planning agent. You MUST NOT implement code, modify configuration, or touch any file other than the single plan file described below. Do not use Edit, Write, or TodoWrite for anything else. Your ONLY outputs are: spawning research sub-agents (Task), asking clarifying questions (AskUserQuestion), and writing the plan file (Write — to the plan file only).
Primary Goal
Produce a planning document (markdown only — no code, no config, no other files) that follows the project's plan template exactly, and write it to the deterministic plan path for this worktree.
Step 0: Resolve the plan path and capture the original request
-
Compute the plan path (one plan per worktree/task — deterministic):
leaf="$(git branch --show-current 2>/dev/null | sed 's#.*/##')" [ -z "$leaf" ] && leaf="plan" mkdir -p tmp/plans echo "tmp/plans/${leaf}.md"The printed path is your plan file. Use it everywhere
<plan-path>appears below. -
Capture the Original Request — verbatim. The original request is whatever the user passed as arguments to this command (
$ARGUMENTS) and/or what they asked for in this conversation. Preserve their exact wording — do not paraphrase, summarize, or omit any part of it.- If a plan file already exists at
<plan-path>(you are re-planning the same task), read it first and reuse its existing## Original Requestsection verbatim instead of re-deriving it.
- If a plan file already exists at
-
Read the plan template in full before doing anything else:
reference/server/constants/templates/plan-template.mdYour output must follow this template's structure section-for-section, in the same order, with no sections removed.
Planning Workflow
You spawn a research sub-agent to explore the codebase; then YOU (the master agent) handle clarification and write the plan. Only you write the plan file. Sub-agents are for research only.
Step 1: Explore (sub-agent)
Spawn a planning sub-agent (Task tool, subagent_type=Plan) to explore the codebase. Its ONLY job is
research — it must NOT write files, run scripts, or ask user questions.
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.
- 24d ago First seen · 114 lines · 20 tokens per session scan B d36f7d97b242
planification is a command published in the GitHub repository vdaubry/bottega (88 stars, last pushed 24d ago), licensed MIT. It adds 20 tokens to every session and 1,272 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.
Other commands, from other repositories
mach12:pr-pre-merge
Run the pre-merge checklist - branch freshness, docs, version, CHANGELOG, tests, CI.
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
mach12:pr-review
Run a comprehensive PR review with independent reviewers and post the results as a structured comment.
mach12:pr-merge
Merge a PR, delete the feature branch, and optionally create a release.
mach12:pr-create
Create a pull request for the current branch with structured description.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.