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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/create-plan)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/create-plan"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/create-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/davistroy/claude-marketplace/create-plan"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/create-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.00022 | $0.06894 |
| Opus 5 | $0.00011 | $0.03447 |
| Sonnet 5 | $0.00004 | $0.01379 |
| Haiku 4.5 | $0.00002 | $0.00689 |
Grade A, and why
create-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 9d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Plan Command
Generate a comprehensive, phased implementation plan from requirements and design documents in the project. This command discovers and analyzes BRDs, PRDs, TDDs, and other specification documents, then produces an actionable IMPLEMENTATION_PLAN.md ready for execution with /implement-plan.
Overview
This command:
- Discovers requirements and design documents in the project
- Surveys the existing codebase to detect tech stack, test infrastructure, and already-implemented features
- Analyzes and synthesizes requirements across all documents, accounting for existing code
- Presents a scope summary (features, phases, assumptions) and waits for user approval before proceeding
- Breaks down work into appropriately-sized phases
- Generates detailed work items with acceptance criteria
- Outputs IMPLEMENTATION_PLAN.md to the repository root
See also:
/plan-improvementsfor codebase-driven improvement analysis./ultra-planfor deep pre-planning when requirements are vague, scope is ambiguous, or the problem needs investigation before a plan can be written. Use/implement-planto execute the generated plan; for large plans (6+ phases or 20+ independent work items), setExecution Mode: ParallelorWorktree-Isolatedin the Phase Summary Table so/implement-plandispatches those phases as concurrent background agents in isolated worktrees.
Input Validation
Arguments: None required
Optional Arguments:
<document-paths>- Specific documents to use (space-separated)--output <path>- Custom output path (default:IMPLEMENTATION_PLAN.md)--phases <n>- Target number of phases (default: auto-calculated)--max-phases <n>- Maximum number of phases to generate (default: 8). Overrides--phasesif--phasesexceeds this limit.--verbose- Show detailed analysis during generation
Examples:
/create-plan # Auto-discover documents
/create-plan PRD.md TDD.md # Use specific documents
/create-plan --phases 5 # Target 5 phases
/create-plan docs/requirements/*.md # Use glob pattern
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.
- 9d ago First seen · 471 lines · 22 tokens per session scan A 87a506812f87
create-plan is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 6,894 once invoked, about $0.0001 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-31.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.