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 skills add wangbin3162/agents-skills --skill plan-and-applygit clone --depth 1 https://github.com/wangbin3162/agents-skillsWrote 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/wangbin3162/agents-skills/plan-and-apply)<a href="https://agentmods.dev/skills/wangbin3162/agents-skills/plan-and-apply"><img src="https://agentmods.dev/badge/skills/wangbin3162/agents-skills/plan-and-apply/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.
<a href="https://agentmods.dev/skills/wangbin3162/agents-skills/plan-and-apply"><img src="https://agentmods.dev/badge/skills/wangbin3162/agents-skills/plan-and-apply.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00107 | $0.01472 |
| Opus 5 | $0.00053 | $0.00736 |
| Sonnet 5 | $0.00021 | $0.00294 |
| Haiku 4.5 | $0.00011 | $0.00147 |
Grade A, and why
plan-and-apply 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 9d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan And Apply
This skill is an upper-layer execution workflow for non-trivial development tasks.
It exists to stop four common failures:
- changing code before understanding the task
- drifting outside the requested scope
- doing large rewrites when a local fix is enough
- claiming completion without verification
Use it to control execution rhythm. Do not use it for simple one-step questions or tiny edits that do not need planning.
When to use
Use this skill when any of these are true:
- the user says
先分析、先规划、不要直接改 - the task spans multiple files or modules
- the task is a migration, refactor, or structured feature implementation
- the task needs a clear task list, progress tracking, or staged rollout
- the user cares about strict boundaries, minimal change, or explicit regression checks
Do not use this skill when:
- the user only wants explanation or brainstorming
- the change is trivial, isolated, and low risk
- the task is pure review with no implementation
Core promise
Follow this order unless the user explicitly asks for a narrower path:
- Read rules first
- Clarify task scope and constraints
- Decide whether planning is required
- Break work into the smallest viable slices
- Apply only the current slice
- Verify the change and do regression checks
- Close out with result, validation, and remaining risk
Step 1: Read rules first
Before implementation, read the project-level instructions that control behavior.
Priority order:
lessons.mdAGENTS.md- task-specific rule files mentioned by the user
- relevant reference implementation or old version
If there is no lessons.md, continue without blocking. Do not invent one.
Step 2: Clarify the task
Before changing anything, answer these questions from local context:
- What is the actual requirement?
- What constraints did the user set?
- What are the main risks?
- What is the simplest viable approach?
- How will the result be verified?
If a key constraint is missing and guessing would be risky, ask a short direct question. Otherwise, proceed with the safest reasonable assumption.
What ships with it
2 files 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.
- 9d ago First seen · 226 lines · 107 tokens per session scan A 37d684dfae23
plan-and-apply is a skill published in the GitHub repository wangbin3162/agents-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,472 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.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…