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/spumer/i-m-senior-developer/plan-reflectgit clone --depth 1 https://github.com/spumer/i-m-senior-developerWhat 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.00290 |
| Opus 5 | $0.00013 | $0.00145 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
plan-reflect 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 2d 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.
What it actually says
Activate the planner-reflect skill and follow its workflow.
Resolve the feature directory from $ARGUMENTS:
- If
$ARGUMENTSis provided — use it as the feature directory. - If
$ARGUMENTSis empty — collect candidate directories from paths explicitly used in the current task and from changed paths reported by Git. Keep only candidates containingPLANNER_EXECUTION.md. - Continue only when exactly one candidate remains. If there are none or several, ask for an explicit feature directory and write nothing. Never choose by modification time.
Run the skill end-to-end: gather the five evidence sources, classify findings into the four update types, mask any PII per the skill's PII section, write to <project-root>/.claude/planner-context.md, and emit a chat summary that always includes a "Lessons learned" block.
If no PLANNER_EXECUTION.md exists anywhere relevant, emit the graceful exit message from the skill's "When evidence is missing" section (nothing to reflect on; run /plan first) and stop without writing.
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.
- 2d ago First seen · 19 lines · 26 tokens per session scan A a31da15c57da
plan-reflect is a command published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 290 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
git
Git operations with intelligent commit messages and workflow optimization.
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.