Borrowing it
Nothing to install: this file belongs to pyrex41/skill-manager. 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/pyrex41/skill-manager/master/.claude/commands/cl/create_plan.mdgit clone --depth 1 https://github.com/pyrex41/skill-managerWrote 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/pyrex41/skill-manager/create_plan)<a href="https://agentmods.dev/commands/pyrex41/skill-manager/create_plan"><img src="https://agentmods.dev/badge/commands/pyrex41/skill-manager/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/pyrex41/skill-manager/create_plan"><img src="https://agentmods.dev/badge/commands/pyrex41/skill-manager/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.00009 | $0.00746 |
| Opus 5.5 | $0.00004 | $0.00298 |
| Sonnet 5.5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
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 2mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Implementation Plan
You are tasked with creating a detailed, actionable implementation plan through collaborative research and iteration.
Philosophy
Be skeptical and thorough. Plans should:
- Eliminate all open questions before finalization
- Be based on deep understanding of the existing codebase
- Include both automated and manual success criteria
- Be iterative - seek feedback at each phase
Process
Phase 1: Context Gathering
- Read all mentioned files completely - Never use limit/offset, you need full context
- Spawn parallel research agents to understand the codebase:
- Use
codebase-locatorto find WHERE relevant code lives - Use
codebase-analyzerto understand HOW specific code works - Use
thoughts-locatorto find existing documentation
- Use
- Present your understanding with focused questions for clarification
Phase 2: Research & Discovery
- Verify any user corrections through new research
- Create a todo list to track exploration
- Spawn concurrent sub-tasks for comprehensive investigation
- Present findings with design options when multiple approaches exist
Phase 3: Plan Structure Development
- Propose phasing before detailed writing
- Seek feedback on organization and granularity
- Identify dependencies between phases
Phase 4: Detailed Plan Writing
Create a markdown document with this structure:
# Plan: [Feature/Task Name]
## Overview
[2-3 sentence summary of what this plan accomplishes]
## Current State Analysis
[What exists today, relevant code locations]
## Desired End State
[Clear description of the goal]
## Implementation Approach
[High-level strategy]
## Phases
### Phase 1: [Name]
**Goal**: [What this phase accomplishes]
**Changes**:
- [ ] Change 1 (`file:line`)
- [ ] Change 2 (`file:line`)
**Success Criteria - Automated**:
- [ ] `make check` passes
- [ ] `make test` passes
- [ ] Specific test case passes
**Success Criteria - Manual**:
- [ ] UI shows expected behavior
- [ ] Edge case X works correctly
### Phase 2: [Name]
[Continue pattern...]
## Open Questions
[MUST be empty before plan is finalized]
## Risks and Mitigations
[Known risks and how to handle them]
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.
- 2mo ago First seen · 122 lines · 9 tokens per session scan A de7c79090991
create_plan is a command published in the GitHub repository pyrex41/skill-manager (4 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 746 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-31.
create_plan compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| create_planpyrex41/skill-manager | Command | 4 | 9mo ago | MIT | A | 9 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |