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/i9wa4/dotfiles/plan-designnpx skills add i9wa4/dotfiles --skill plan-designgit clone --depth 1 https://github.com/i9wa4/dotfilesWrote 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/i9wa4/dotfiles/plan-design)<a href="https://agentmods.dev/skills/i9wa4/dotfiles/plan-design"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/plan-design.svg" alt="Measured on agentmods" 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 | $0.00090 | $0.00448 |
| Opus 5 | $0.00045 | $0.00224 |
| Sonnet 5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
plan-design 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 4d 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.
What it actually says
Plan Design
Owns implementation-plan authoring and durable task tracking for plan-ready tasks: ambiguity reduction, option framing, multi-source synthesis, review gates, task artifacts, evidence logs, and handoff/resume.
Use artifacts for non-code artifact lifecycle, local mkmd storage,
artifact discovery/reuse, and Secret-Gist delivery mechanics. This skill owns
planning semantics and evidence expectations, not artifact storage policy.
Follow the output language designated by the active runtime/session policy or explicit request. Do not establish an independent language policy in this skill.
1. Workflow
- Inspect the relevant files, current repo conventions, and
git status. - Read Plan Authoring before changing behavior or giving detailed instructions.
- If the task is fuzzy or has multiple viable approaches, read Brainstorming and stabilize the direction before drafting the execution plan.
- If plan terms, states, conditions, cause categories, or mitigation names are
ambiguous, use
clarify-conceptsbefore the plan language hardens. - Make the smallest scoped change that satisfies the request.
- Run the checks named in the plan authoring guide or the nearest repo harness.
- Report verification results and any remaining risk.
2. References
What ships with it
8 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.
- evals/eval.yaml 508 B
- evals/tasks/negative-trigger-1.yaml 426 B
- evals/tasks/positive-trigger-1.yaml 399 B
- evals/tasks/positive-trigger-2.yaml 400 B
- evals/tasks/positive-trigger-3.yaml 532 B
- references/brainstorming.md 2.2 KB
- references/durable-task-tracking.md 5.8 KB
- references/plan-authoring.md 11 KB
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.
- 4d ago First seen · 49 lines · 90 tokens per session scan A 2ee85fa45db8
plan-design is a skill published in the GitHub repository i9wa4/dotfiles (11 stars, last pushed 4d ago), licensed MIT. It adds 90 tokens to every session and 448 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-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…