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/redhuntlabs/wizard/executing-a-plan-step-by-stepnpx skills add redhuntlabs/wizard --skill executing-a-plan-step-by-stepgit clone --depth 1 https://github.com/redhuntlabs/wizardWrote 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/skills/redhuntlabs/wizard/executing-a-plan-step-by-step)<a href="https://agentmods.dev/skills/redhuntlabs/wizard/executing-a-plan-step-by-step"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/executing-a-plan-step-by-step.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.00031 | $0.01244 |
| Opus 5 | $0.00015 | $0.00622 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
executing-a-plan-step-by-step 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing a Plan Step by Step
What this does
Executes an implementation plan step-by-step with discipline: read what the step says, make the change, run the step's verification, mark done. On verification failure, stop and diagnose before moving on.
When to use
- You have a written implementation plan (from writing-an-implementation-plan or equivalent)
- You're starting or resuming execution
- The plan has multiple steps with verifications
Do not use when
- There's no written plan (write one first; see writing-an-implementation-plan)
- The plan has no per-step verifications (fix the plan first)
- You're doing exploratory work without a clear destination
What you bring (Inputs)
- The written plan
- Working dev environment
- Any credentials/access the plan calls for
What you get (Output)
A completed implementation, plus an updated plan document with each step marked done and any deviations recorded.
How it works (Steps)
This is a chained workflow. Each step is a sub-cycle.
Stages
Stage 1: Pick up where you left off
Open the plan. Find the first step that's not marked done. If the plan has no marks yet, start at step 1.
If you're resuming after a break, re-read the steps that were already done — you need that context loaded back into your head.
Stage 2: Per-step cycle
For each step:
Step.A: Read the step in full
What does this step say to do? What does it say is the verification? What files does it touch?
If the step is unclear, do NOT improvise. Update the plan first to clarify, then execute the clarified step.
Step.B: Read the surrounding code
Before touching anything, read the file(s) the step affects in their current state. Skipping this is the #1 cause of "AI confidently wrote the wrong thing."
Step.C: Make the change
Make the smallest change that satisfies the step. Do NOT make adjacent improvements ("while I'm here..."). Adjacent changes go in a side notebook for later, not in this commit.
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 · 148 lines · 31 tokens per session scan A a430efdb5859
executing-a-plan-step-by-step is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,244 once invoked, about $0.0002 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 skills, from other repositories
fastapi
FastAPI - 高性能 Python Web API 框架.
glances
Skill "glances" from CN-big-cabbage/github-skill-distiller, covering glances 跨平台系统监控工具, 技能概述, 使用流程, 关键章节导航 and ai 助手能力.
lazydocker
本技能帮助用户通过 lazydocker 的终端 UI 界面管理 Docker 容器、镜像、卷和网络，支持以下场景：.
fzf
Skill "fzf" from CN-big-cabbage/github-skill-distiller, covering fzf 通用命令行模糊查找器, 技能概述, 使用流程, 关键章节导航 and ai 助手能力.
paper-checking
论文查重系统 - 一亿字次级论文库秒级查重，支持纵向查重和横向查重.
you-get
网页媒体下载助手 - 从YouTube、Bilibili等网站下载视频、音频、图片.