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 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/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/i9wa4/dotfiles/plan-design"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/plan-design.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.00090 | $0.00451 |
| Opus 5.5 | $0.00036 | $0.00180 |
| Sonnet 5.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 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.
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.
This skill owns planning semantics and evidence expectations, not artifact storage or delivery mechanics. Leave a durable artifact of your work; where and how it is created, reused, discovered, and delivered is governed elsewhere in this environment.
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.3 KB
- references/durable-task-tracking.md 5.0 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.
- 1mo ago Changed · +1 lines 581b889041d6
- 1mo ago Changed 184d8ee41620
- 2mo ago First seen · 49 lines · 90 tokens per session scan A 2ee85fa45db8
plan-design is a skill published in the GitHub repository i9wa4/dotfiles (12 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 451 once invoked, about $0.0004 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
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
model-triage
Adopt the per-issue model-selection convention in a repo — tier every open issue, apply the model: labels, board field, and callouts behind an approval gate. Also runs in maintenance mode to sweep up unlabeled issues and label/field drift.
autopilot-triage
Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.
create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
plan-phase
Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.