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 skills/nikeyes/stepwise-dev/iterate-plannpx skills add nikeyes/stepwise-dev --skill iterate-plangit clone --depth 1 https://github.com/nikeyes/stepwise-devWhat 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.00014 | $0.02237 |
| Opus 5 | $0.00007 | $0.01118 |
| Sonnet 5 | $0.00003 | $0.00447 |
| Haiku 4.5 | $0.00001 | $0.00224 |
Grade A, and why
iterate-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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate Implementation Plan
You are tasked with updating existing implementation plans based on user feedback. You should be skeptical, thorough, and ensure changes are grounded in actual codebase reality.
Initial Response
When this command is invoked:
Input: $ARGUMENTS
-
Parse $ARGUMENTS to identify:
- Plan file path (e.g.,
thoughts/shared/plans/2025-10-16-feature.md) - Requested changes/feedback (remaining text after the file path)
- Plan file path (e.g.,
-
Handle different input scenarios:
If $ARGUMENTS is empty (no plan file or feedback):
I'll help you iterate on an existing implementation plan. Which plan would you like to update? Please provide the path to the plan file and changes to make. Usage: /stepwise-core:iterate-plan [plan-file-path] [changes to make] Example: /stepwise-core:iterate-plan thoughts/shared/plans/2025-10-16-feature.md add error handling phase Tip: You can list recent plans with `ls -lt thoughts/shared/plans/ | head`Wait for user input, then re-check for feedback.
If $ARGUMENTS contains only plan file path (no feedback):
I've found the plan at [path]. What changes would you like to make? For example: - "Add a phase for migration handling" - "Update the success criteria to include performance tests" - "Adjust the scope to exclude feature X" - "Split Phase 2 into two separate phases"Wait for user input.
If $ARGUMENTS contains BOTH plan file AND feedback:
- Proceed immediately to Step 1
- No preliminary questions needed
Process Steps
Step 1: Read and Understand Current Plan
- Read the existing plan file COMPLETELY:
- Use the Read tool WITHOUT limit/offset parameters
- Understand the current structure, phases, and scope
- Note the success criteria and implementation approach
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 · 282 lines · 0 tokens per session scan A cf4f3afdabe8
iterate-plan is a skill published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed 14d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,237 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…