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/anilcancakir/claude-code-plugins/my_plangit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/my_plan)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugins/my_plan"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugins/my_plan.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.00026 | $0.00573 |
| Opus 5 | $0.00013 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
my_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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/my_plan - Implementation Planning
Create detailed, actionable implementation plans before coding.
Usage
/my_plan [feature description]
/my_plan --tdd [feature description]
Arguments
--tdd- Enable TDD mode (each task includes RED-GREEN-REFACTOR structure)[feature description]- What you want to build
Examples
/my_plan add user authentication with JWT
/my_plan --tdd implement order management system
/my_plan migrate users table to new schema
/my_plan add real-time notifications with WebSockets
What Happens
-
Parse Arguments
- Check for
--tddflag - Extract feature description
- Detect if project uses TDD by default
- Check for
-
Spawn Planner Agent
- Uses Opus model for deep reasoning
- Has access to all project tools and MCP servers (including Serena)
-
Codebase Analysis
- Explores project structure
- Identifies patterns and conventions
- Finds related existing code
- Maps dependencies
-
Design Solution
- Breaks feature into phases
- Creates atomic, verifiable tasks
- Includes verification steps
- Adds TDD structure if enabled
-
Create Plan File
- Saves to
.claude/plans/{timestamp}-{slug}.md - Returns summary for user approval
- Saves to
Plan Location
Plans are saved to:
.claude/plans/{YYYYMMDD}-{HHMMSS}-{slug}.md
Example: .claude/plans/20260126-143000-user-authentication.md
Next Steps After Planning
- Review the plan - Check the generated plan file
- Approve - Type "approve" to mark ready for execution
- Execute - Run
/my_execute [plan-file]to implement
Rules
- Plans include specific file paths for all tasks
- Every task has a verification step
- TDD mode adds RED-GREEN-REFACTOR to each implementation task
- Planner asks clarifying questions rather than assuming
- No time estimates (focus on what, not when)
Workflow Integration
/my_plan → Review → Approve → /my_execute
│ │
└──────── TDD Mode ────────────┤
↓
RED-GREEN-REFACTOR
per task
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.
- 3d ago First seen · 93 lines · 26 tokens per session scan A 3040b4df16bf
my_plan is a command published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 573 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
debug
Systematic debugging with hypotheses and evidence gathering.
health
Run the Self-Star Doctor - a green/yellow/red health board across all 7 junctions of the self- loop.
plan-new
Plan a complex project with discovery, structure, and kill criteria.
create-hook
Create a new custom automation hook.
remember
Explicitly save something to memory as an experience.
context-stats
Show context window usage, active tier, and system stats.