Borrowing it
Nothing to install: this file belongs to bakabaka91/claude-baton. 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/bakabaka91/claude-baton/main/.claude/commands/plan.mdgit clone --depth 1 https://github.com/bakabaka91/claude-batonWrote 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/bakabaka91/claude-baton/plan)<a href="https://agentmods.dev/commands/bakabaka91/claude-baton/plan"><img src="https://agentmods.dev/badge/commands/bakabaka91/claude-baton/plan.svg" alt="Measured on agentmods" 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.00000 | $0.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
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 4d 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
Create an implementation plan for the described feature or change. Do NOT write any code.
$ARGUMENTS
Steps
- Read PLAN.md for full project context
- Read CLAUDE.md for constraints and current state
- Read all source files relevant to the requested change
- Produce a structured plan:
Plan: [Feature Name]
Context: Why this change is needed
Scope: What's in and out
Steps:
- [Numbered steps with file paths]
Files to modify:
path/file.ts— what changes and why
Files to create:
path/file.ts— purpose
Tests needed:
- [Test cases to add/modify]
Risks:
- [What could go wrong]
Constraints check:
- No git branch manipulation
- Single SQLite DB (no per-project files)
- stdio transport only
- No API keys / anthropic SDK imports
- Max 4 dependencies
- CLAUDE.md ordering preserved
- sql.js WASM only
- ~200 line token budget for managed block
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.
- 4d ago First seen · 42 lines · 0 tokens per session scan A bea8c6d59fba
plan is a command published in the GitHub repository bakabaka91/claude-baton (25 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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-01.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.