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/evan043/claude-cli-advanced-starter-pack/phase-dev-plan.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/phase-dev-plan.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/phase-dev-plan.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/phase-dev-plan.template.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.00000 | $0.05729 |
| Opus 5 | $0.00000 | $0.02864 |
| Sonnet 5 | $0.00000 | $0.01146 |
| Haiku 4.5 | $0.00000 | $0.00573 |
Grade A, and why
phase-dev-plan.template 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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Create phased development plans with 95%+ success probability options:
- label: "Small (1-2 phases)" description: "Quick feature or bug fix"
- label: "Medium (3-4 phases)" description: "Standard feature implementation"
- label: "Large (5+ phases)" description: "Complex multi-system changes"
Phased Development Plan Generator
Create comprehensive, executable development plans that maximize success probability.
NEW EPIC-HIERARCHY ARCHITECTURE:
- Supports parent roadmap context via --parent-roadmap flag
- Supports parent epic context via --parent-epic flag
- Includes parent_context in PROGRESS.json
- Reports PHASE_DEV_COMPLETE to parent when all phases complete
- Uses src/phase-dev/completion-reporter.js for parent notification
🚨 MANDATORY FILE CREATION - DO NOT SKIP
CRITICAL: Every phase-dev-plan MUST create ALL of these files. Skipping ANY file is a failure.
Exploration Documentation (REQUIRED FIRST - Step 2)
Before creating PROGRESS.json, you MUST create these 6 files in .claude/exploration/{slug}/:
| File | Purpose | Required |
|---|---|---|
EXPLORATION_SUMMARY.md |
Overview + statistics | ✅ YES |
CODE_SNIPPETS.md |
Extracted code examples | ✅ YES |
REFERENCE_FILES.md |
File paths + line numbers | ✅ YES |
AGENT_DELEGATION.md |
Agent assignments per task | ✅ YES |
PHASE_BREAKDOWN.md |
Full phase/task detail | ✅ YES |
findings.json |
Machine-readable data | ✅ YES |
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 · 646 lines · 0 tokens per session scan A 09cf827fb6c8
phase-dev-plan.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,729 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].