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/lancewillett/ai-plugins/five-stepsnpx skills add lancewillett/ai-plugins --skill five-stepsgit clone --depth 1 https://github.com/lancewillett/ai-pluginsWhat 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.00091 | $0.00449 |
| Opus 5 | $0.00046 | $0.00225 |
| Sonnet 5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
five-steps 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
Five steps
Walk the target through all five steps, then edit it.
Why this matters
The natural instinct is to automate first. The framework forces the harder questions earlier: do we even need this requirement? Can we delete this step entirely? Only after pruning and simplifying does automation make sense.
Scope: processes, tools, products, and systems you own.
The framework
Adapted from Elon Musk's five-step "algorithm" for improving a process.
- Question every requirement—Is this necessary? Who asked for it? Would we add it if starting fresh?
- Delete parts or processes—Remove the unnecessary. Add things back 10% of the time, or you're not deleting enough.
- Simplify or optimize—Make what remains easier to work with.
- Accelerate cycle time—Speed up without sacrificing quality.
- Automate—Last, not first.
Application areas
Shaping new plans
Use the 5 steps as a checklist when co-creating plans with AI or with the team. Before any plan gets a green light, walk it through all 5 steps.
Reviewing existing systems
Periodically audit your systems against the framework:
- CI/CD pipelines—what steps can be deleted or simplified?
- Triage workflows—are we questioning requirements or just adding process?
- Testing infrastructure—what's over-engineered?
- Reporting and metrics—do we need all these dashboards?
Make the changes
Edit the target in place: cut what step 2 deleted, rewrite what survived.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 46 lines · 91 tokens per session scan A 165ec34e3f1e
five-steps is a skill published in the GitHub repository lancewillett/ai-plugins (2 stars, last pushed 17d ago), licensed MIT. It adds 91 tokens to every session and 449 once invoked, about $0.0005 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
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…