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/create-plannpx skills add maxedapps/agent-skills --skill create-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.00086 | $0.00859 |
| Opus 5 | $0.00043 | $0.00430 |
| Sonnet 5 | $0.00017 | $0.00172 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
create-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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Plan
Hard rules
- Plan only — never implement.
- Allowed writes:
.plans/<kebab-name>.md, and.reviews/*-decomplex.mdwhen needed. - Evidence-backed. Smallest design. No speculative scope.
- Ask user on material ambiguity (scope/behavior/architecture/migration/risk/complexity). No shaky assumptions.
- Delegate by default for research and review when safe. “Small/easy” ≠ skip subagents.
- Leverage subagents — built-in, extensions/plugins, or skills. Follow
use-subagentspolicy; use native subagents, extensions / plugins, or other skills - Main agent owns synthesis, plan writes, dispositions, delivery.
- Child/reviewer output = evidence, never acceptance. Findings never auto-enter the plan.
- Prefer simpler fixes. Stuck review (2 failed rounds / recurrence / no progress) → ask user.
Load or stop
- Before draft: read
assets/implementation-plan-template.md. - Before finalize (and after material edits): read
references/plan-quality-checklist.md. - Missing resources → stop. Don’t invent substitutes.
Tasks must have
- Stable IDs
- Change as bullets (one concrete edit/behavior each)
- Starts-at paths/symbols (non-exhaustive)
- Exact verify commands + expected signals
- Each behavior-changing task names an existing/planned test path or suite, the observable behavior, boundary, or regression it protects, and the narrowest credible repository-conventional layer; or justifies omitting automation and gives alternate validation
- Omit empty optionals
- Key files table: path · why · plan impact
Sequence
- Frame — request, repo instructions, existing plans → outcome, scope, non-goals, risks, validation. Don’t deep-explore in parent when a research lane can.
- Load template.
- Research — enumerate questions; delegate by default (one question/scope/stop per lane). Inspect relevant existing tests, framework/configuration, and repository commands. External only if decision-relevant. Verify critical claims.
- Resolve gates — still ambiguous? ask user before drafting as fact.
- Synthesize — smallest approach; map findings → decisions/tasks/checks/non-goals/gates; drop fluff.
- Draft — adapt template; flat tasks default; phases only for real boundaries; no review ledgers in the handoff.
- Complexity — structural draft →
decomplexPrevention if available, else built-in gate. Complexity-increasing accept → triage; doubt → ask user. - Review — consequential plans: delegate fresh independent reviewers → disposition (
Accept/Validate/Reject/Ask user/Block) → revise → re-review untilClear. Small/unavailable: parent checklist + independence limit. - Checklist → deliver — save under
.plans/(or chat + no-write reason). Report path, gates, decisions, fallbacks, risks.
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.
- 3d ago First seen · 66 lines · 86 tokens per session scan A fab586e4b944
create-plan is a skill published in the GitHub repository maxedapps/agent-skills (58 stars, last pushed 18d ago), licensed MIT. It adds 86 tokens to every session and 859 once invoked, about $0.0004 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.
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…