five-steps

five-steps is a skill for Claude Code, Codex from lancewillett/ai-plugins. It costs 91 tokens per session (449 once invoked), scanned A, original, MIT.

A five-step method for improving a plan, process, tool, or product: question it, delete unnecessary parts, simplify it, speed it up, then automate it.

In plain words
What is it for?
Use it to review development workflows, CI/CD pipelines, triage processes, products, and new project plans.
Why use it?
It helps prevent teams from automating work that could first be removed or made simpler.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also agents/openai.yaml present.

Part of the five-steps plugin — 1 skill shipped together

Good fit Use it to review development workflows, CI/CD pipelines, triage processes, products, and new project plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lancewillett/ai-plugins/five-steps
Install

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.

Any agent
npx skills add lancewillett/ai-plugins --skill five-steps
Clone the repo
git clone --depth 1 https://github.com/lancewillett/ai-plugins

Made for: Claude Code, Codex.

Or install five-steps, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for five-steps

README.md
[![agentmods](https://agentmods.dev/badge/skills/lancewillett/ai-plugins/five-steps/github.svg)](https://agentmods.dev/skills/lancewillett/ai-plugins/five-steps)
Your own site
<a href="https://agentmods.dev/skills/lancewillett/ai-plugins/five-steps"><img src="https://agentmods.dev/badge/skills/lancewillett/ai-plugins/five-steps/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for five-steps

Your own site · 80×15
<a href="https://agentmods.dev/skills/lancewillett/ai-plugins/five-steps"><img src="https://agentmods.dev/badge/skills/lancewillett/ai-plugins/five-steps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00449
Opus 5.5 $0.00036 $0.00180
Sonnet 5.5 $0.00018 $0.00090
Haiku 4.5 $0.00009 $0.00045

Measured 1mo ago against content hash 165ec34e3f1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/five-steps/skills/five-steps/SKILL.md · 46 lines

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.

  1. Question every requirement—Is this necessary? Who asked for it? Would we add it if starting fresh?
  2. Delete parts or processes—Remove the unnecessary. Add things back 10% of the time, or you're not deleting enough.
  3. Simplify or optimize—Make what remains easier to work with.
  4. Accelerate cycle time—Speed up without sacrificing quality.
  5. 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.

Files

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.

Changes

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.

  1. 1mo ago First seen · 46 lines · 91 tokens per session scan A 165ec34e3f1e

Subscribe to this mod's changes

five-steps is a skill published in the GitHub repository lancewillett/ai-plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 449 once invoked, about $0.0004 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens