Borrowing it
Nothing to install: this file belongs to phuryn/pm-brain. 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/phuryn/pm-brain/main/.claude/skills/pm-brain/scaffold/.claude/commands/plan.mdgit clone --depth 1 https://github.com/phuryn/pm-brainWrote 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/phuryn/pm-brain/plan)<a href="https://agentmods.dev/commands/phuryn/pm-brain/plan"><img src="https://agentmods.dev/badge/commands/phuryn/pm-brain/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/phuryn/pm-brain/plan"><img src="https://agentmods.dev/badge/commands/phuryn/pm-brain/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.00000 | $0.00499 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan
Turn a new team objective into a concrete plan: what we know, what we assume, who to interview, which hypotheses to open, which experiments to run, what decision would unlock execution.
Input
An objective statement. Example: /plan reduce onboarding drop-off by 20% in Q3.
Loads
knowledge/strategy.md(priorities, non-goals, north-star, tensions)knowledge/product/metrics.md(current values, definitions)knowledge/product/features/filtered to ones touching the objectiveknowledge/users/insights.md, relevantpersonas.md/segments.md- All active
hypotheses/in the area decisions/filtered to relevant prior commitmentsstakeholders/filtered to people who'd influence or block the planrules/discovery.md,rules/prioritization.md,rules/data.md
Updates
- A draft
ingestion/adhoc/<date>-plan-<slug>.mdcapturing the planning session hypotheses/<slug>.md— drafts for any value/usability/feasibility/viability/other risk that needs testing (status:candidate)decisions/<date>-<slug>.md— drafts for go/no-go points (status:pending)stakeholders/<slug>.md § Open asks— drafts for the alignment conversations the plan implies
Nothing committed without operator confirmation per autonomy mode.
Surfaces
Six blocks, in this order:
- What we already know — citations to insights, hypotheses, decisions, metrics
- Assumption vs evidence — explicitly tagged, with provenance for each
- Who to interview — segments, personas, specific named users; recent coverage gaps
- Hypotheses to open — across the 5 risk areas, with the test for each
- Experiments to run — sequenced, with success criteria and what would invalidate
- Decision points — the go/no-go moments and what evidence would unlock each
Plus:
- Constraints from
strategy.md § Non-goalsthat bound the plan - Stakeholder alignment conversations the plan requires (linked to
/prep) - One paragraph on what would make the plan unwise (so the operator can falsify it early)
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 · 45 lines · 0 tokens per session scan A 9a2bc45a9503
plan is a command published in the GitHub repository phuryn/pm-brain (941 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 499 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-08-30.
Other commands, from other repositories
youtube
Extract transcript, metadata, and top comments from a YouTube video - summarized via Gemini (free tier) or Grok and saved to vault. Add --visual to also read the video's frames (scene detection).
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
x-read
Deep-read an X (Twitter) post via Grok xsearch - verbatim post, thread, TL;DR, claims, reply sentiment, voices to watch.
obsidian-checkin
Ask the owner whether old people and project notes still hold - shows what each note says and when it was last checked, re-asks until answered, saves the news.
obsidian-distill
Condense a long note or source into key claims, each tagged with provenance back to the exact source block it came from.
obsidian-merge
Merge two near-duplicate notes found by /obsidian-health into one - dry run by default, redirects the retired note rather than deleting it.