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.
npx agentmods add commands/primeline-ai/universal-planning-framework/plan-newgit clone --depth 1 https://github.com/primeline-ai/universal-planning-frameworkWrote 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/primeline-ai/universal-planning-framework/plan-new)<a href="https://agentmods.dev/commands/primeline-ai/universal-planning-framework/plan-new"><img src="https://agentmods.dev/badge/commands/primeline-ai/universal-planning-framework/plan-new.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 | $0.00009 | $0.04605 |
| Opus 5 | $0.00005 | $0.02302 |
| Sonnet 5 | $0.00002 | $0.00921 |
| Haiku 4.5 | $0.00001 | $0.00460 |
Grade A, and why
plan-new 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 5d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Plan
You are creating a plan for: $ARGUMENTS
Follow the Universal Planning Framework. Execute ALL stages in order. No stage may be skipped or replaced by inline text.
STRICT READ-ONLY RULE
During /plan-new execution, ONLY the plan file may be edited. No other files may be created, edited, or deleted. No Bash commands that make changes. Only: Read, Grep, Glob, Explore/Plan Agents, AskUserQuestion, Skill (for interview/refine/review), TodoWrite (for phase/task tracking). Violation = abort planning.
This replaces EnterPlanMode/ExitPlanMode to avoid repeated UI previews that clutter the screen.
Step 0: Planning Mode Selection
Before starting, ask the user how they want to work:
AskUserQuestion:
"How would you like to work through the plan?"
Options:
1. "Manual - I'll go through each phase step by step"
(User controls each phase, chooses interactive or self-interview)
2. "Autonomous - you handle everything independently"
(All phases autonomous, interview in self-mode)
3. "Autonomous with interactive interview"
(All phases autonomous, but I answer the interview myself)
Store the selected mode and follow it through all stages.
Stage 0.pre: DSV (Quick Reasoning Check)
MANDATORY - Before any planning, run DSV on the task itself:
- Decompose: What are the 2-3 key claims in this request?
- Suspend: What alternative interpretation haven't I considered?
- Validate: Which claim am I least sure about? Validate that first.
If Suspend reveals a plausible alternative: raise it before proceeding.
Document DSV results in the plan file under ## DSV Pre-Check.
Stage 0: Discovery (Before Planning)
Determine which of the 12 checks to run. Use the intelligence rule: skip checks you can articulate a reason for skipping.
Priority tiers:
- Always: 0.1 Existing Work, 0.7 Feasibility, 0.9 Better Alternatives (AHA Effect)
- Always (coding domains): + 0.3 Official Docs
- Usually: 0.2 Factual Verification, 0.3 Official Docs, 0.8 ROI
- Context-dependent: 0.4 Updates Scan, 0.5 Best Practices, 0.6 Deep Research, 0.10 Competitive, 0.11 Constraint Discovery, 0.12 People Risk
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.
- 5d ago First seen · 408 lines · 9 tokens per session scan A 68a093e858de
plan-new is a command published in the GitHub repository primeline-ai/universal-planning-framework (45 stars, last pushed 11d ago), licensed MIT. It adds 9 tokens to every session and 4,605 once invoked, about $0.0000 per session on Opus 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
bug-council
Bug Council — spawn 5 diagnostic specialists in parallel to analyze a hard bug from multiple angles, then synthesize a root cause and fix recommendation.
plan
Plan from the current Fathom session, grounded in a structured intent.
discovery-ping
Discovery-plugin self-test. Exercises the plugin-shipped slash command path so we can capture commandsource/expansiontype values via the hook dumps.
validate
Run the FPF Reference MCP validation contract (index status + tool list + compact route query) and report layered evidence.
pr-check-and-fix
Triage failing PR checks and apply fixes using limps workflows and scripts only.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.