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 maxedapps/agent-skills --skill implement-plangit clone --depth 1 https://github.com/maxedapps/agent-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/maxedapps/agent-skills/implement-plan)<a href="https://agentmods.dev/skills/maxedapps/agent-skills/implement-plan"><img src="https://agentmods.dev/badge/skills/maxedapps/agent-skills/implement-plan/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/maxedapps/agent-skills/implement-plan"><img src="https://agentmods.dev/badge/skills/maxedapps/agent-skills/implement-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 82 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00067 | $0.00825 |
| Opus 5.5 | $0.00027 | $0.00330 |
| Sonnet 5.5 | $0.00013 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
implement-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 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
Hand off
Inside herdr (HERDR_ENV=1), hand the plan to a new agent unless you are the implementer or were told to implement it here (see orchestrate-agents):
- Create a worktree (see use-worktrees). Copy the plan and ADR into it if they aren't committed.
- Open the worktree in a new pane of your current herdr workspace, tagged as your worker (see use-worktrees), and start an agent of your kind there. Never create a new workspace or tab for it. Give it the plan path, any context the plan lacks, and: "You are the implementer. Use implement-plan in this checkout; don't hand off."
- Step in only when it is blocked or asks something.
- When it reports every task implemented and verified, start the reviewer the same way, in its own tagged pane, on the same worktree. Tell it the plan path, the implementer's pane, and: "You are the reviewer. Follow implement-plan's Review round and settle findings directly with the implementer. Don't edit files."
- When the review is settled, quit the reviewer and close its pane. Bring open disagreements to the user.
- When the implementer reports its PR, check the branch is fully pushed, quit the agent, close its pane, remove the worktree (see use-worktrees), and report the PR.
Otherwise, implement it yourself.
Implement
- Read the plan and its ADR. If something is unclear or looks wrong, ask before building on it.
- Work through the tasks in order. Build the simplest thing that meets each task, with no extra layers, options, or defensive code for cases that can't happen.
- Hand complex or parallel tasks to subagents.
- Add or update tests only where they protect behavior that matters (see awesome-tests).
- Verify every task yourself: run the checks the plan names, and check anything with a UI in a real browser with agent-browser. Set up any service or test data a check needs; don't leave testing to the user.
- Keep the plan file current. If you deviate, update the plan, or write a new ADR if the decision changed.
- When all tasks are done, get the review round. If the plan was handed to you, say you're ready and wait for the reviewer; otherwise start one yourself (its own herdr pane, or a subagent outside herdr).
- Commit, push, and open a pull request that says what changed, how you verified it, and what the review changed.
- Stop dev servers and close browsers. Leave the worktree to whoever created it.
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.
- 1mo ago Changed 1cb6f1adc5e3
- 1mo ago Changed · +26 lines · +11 tokens per session de0f31497c4c
- 1mo ago Changed · -32 lines · -2 tokens per session 1659a9379986
- 1mo ago Changed · -45 lines 067dfe74e1a1
- 1mo ago Changed · +1 lines de0d6047462b
- 2mo ago First seen · 97 lines · 58 tokens per session scan A 10f891c29129
implement-plan is a skill published in the GitHub repository maxedapps/agent-skills (60 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 825 once invoked, about $0.0003 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-30.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…