Borrowing it
Nothing to install: this file belongs to littlebearapps/untether. 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/littlebearapps/untether/master/.claude/commands/plan.mdgit clone --depth 1 https://github.com/littlebearapps/untetherWrote 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/littlebearapps/untether/plan)<a href="https://agentmods.dev/commands/littlebearapps/untether/plan"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/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/commands/littlebearapps/untether/plan"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/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.00010 | $0.01541 |
| Opus 5.5 | $0.00004 | $0.00616 |
| Sonnet 5.5 | $0.00002 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
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 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /plan. /plan turns an idea into a grounded, phased plan
pack under docs/plans/<slug>/. It is the scope half of delivery — read-only
on code, it produces the artefact that /implement later executes one phase at a
time.
User input: $ARGUMENTS
Untether adaptations (read first)
Load .claude/rules/workflow-commands.md (routing + cross-cutting rules). For
/plan:
- Authority: writes plan docs only, never code. Runs in plan mode by nature.
- Reuse, don't duplicate. The blueprint MUST include a reuse map citing existing Untether files/skills to reuse before proposing new code. A plan with no reuse map is incomplete.
- Research gate. Never plan provider/API-sensitive or current-truth work from
memory — route it to the global
/researchand capture findings underdocs/findings/<YYYY-MM-DD>-<slug>.md, then cite them. - Date every current-state claim. State-of-the-world facts drift; stamp them.
- Note on location:
docs/plans/is gitignored — plan packs are local by design (this very plan lives there untracked)./implementreads them locally; only committed code lands in git.
Sub-commands
| Form | Action |
|---|---|
/plan incoming/<file>.md |
Plan from a captured idea file |
/plan #NN |
Plan from a GitHub issue |
/plan <inline idea text> |
Plan from a one-line idea |
/plan <slug> --status |
Read-only: print an existing pack's phase table + progress |
/plan --help |
Usage, then stop |
Flow
P-1. Redirect check (don't plan the wrong thing)
Classify the idea first:
- A defect / regression → STOP, route to
/fix(or/debugto understand). A plan pack is for net-new capability, not bug work. - An existing pack (a
docs/plans/<slug>/already covers this) → STOP, don't re-plan; offer--statusor route to/implementfor the next phase.
P-2. Brainstorm intent (superpowers)
Invoke superpowers:brainstorming via the Skill tool to explore intent,
requirements, and design before mapping code. Capture the sharpened problem
statement and success criteria.
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 · 128 lines · 10 tokens per session scan A aba338c3a237
plan is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,541 once invoked, about $0.0000 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 commands, from other repositories
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
research
Research a technical or product question.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
sprint-plan
Generate or update sprint plan.
tech-debt
Track and prioritize technical debt.
santa-loop
Adversarial dual-review convergence loop — two independent model reviewers must both approve before code ships.