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/maxedapps/agent-skills/implement-plannpx skills add maxedapps/agent-skills --skill implement-plangit clone --depth 1 https://github.com/maxedapps/agent-skillsWhat 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.00058 | $0.01314 |
| Opus 5 | $0.00029 | $0.00657 |
| Sonnet 5 | $0.00012 | $0.00263 |
| Haiku 4.5 | $0.00006 | $0.00131 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
Hard rules
- Stay on the plan’s required outcome. Discovery/review do not add scope.
- Prefer the smallest behavior-preserving change. Skip unnecessary abstractions/tests/safeguards.
- Delegate by default when safe. “Small/easy” is not a reason to skip subagents.
- Leverage subagents — built-in, extensions/plugins, or skills. Follow
use-subagentspolicy; use native subagents, extensions / plugins, or other skills - Main agent owns: tracker, integration, dispositions, acceptance, user comms, cleanup.
- Child handoffs = evidence, never acceptance. Inspect diffs; rerun checks.
- Findings /
decomplexrecs never auto-create work — disposition first. - Material doubt, scope/risk choices, or stuck review loops → ask user.
- Never fake
Complete.
Startup (blocking)
- Read the full plan (offset if truncated).
- Read
assets/progress-tracker-template.mdwith the file tool (memory doesn’t count). - Leverage subagents — built-in, extensions/plugins, or via skills.
- Copy/adapt tracker into the plan or a standalone file.
- Map every actionable plan requirement → tracker rows (split compound work into tasks/subtasks).
- Record
Template loaded from: implement-plan/assets/progress-tracker-template.md. - Only then implement.
On resume: repeat startup and reconcile. Missing template → stop.
Task loop
For each dependency-ready task/subtask (delegate by default):
- Analyze — read starts-at paths, callers, tests; research only if needed (
web-researchwhen third-party/current behavior is uncertain). - Implement — smallest change that satisfies the row; stay in ownership; record deviations.
- Check — targeted tests + applicable lint/typecheck/build/migration/browser (
agent-browserfor UI). - Review — independent
code-reviewwhen the task crosses a real boundary, or when the batch/phase completes; always for final full-plan review. - Disposition findings:
Fix now·Validate·Reject·Ask user·Block- Fix accepted items (delegate); rerun checks; focused re-review until
Clear - Complexity-increasing fix →
decomplextriage if available, else built-in gate; doubt → ask user - Two failed rounds / recurrence / no progress → ask user
- Update tracker —
Verifiedneeds evidence;Descopedneeds user approval. - Cleanup lane resources per
use-subagents(and launcher runtime cleanup, e.g. Piclean, if used) — no unaccounted workflow-owned resources. - Next ready task/subtask.
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 · 97 lines · 58 tokens per session scan A 10f891c29129
implement-plan is a skill published in the GitHub repository maxedapps/agent-skills (58 stars, last pushed 17d ago), licensed MIT. It adds 58 tokens to every session and 1,314 once invoked, about $0.0003 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-30.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.