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 fmind/dot --skill implementation-plangit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/implementation-plan)<a href="https://agentmods.dev/skills/fmind/dot/implementation-plan"><img src="https://agentmods.dev/badge/skills/fmind/dot/implementation-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/fmind/dot/implementation-plan"><img src="https://agentmods.dev/badge/skills/fmind/dot/implementation-plan.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.00018 | $0.00900 |
| Opus 5.5 | $0.00007 | $0.00360 |
| Sonnet 5.5 | $0.00004 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
implementation-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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan
Design the smallest sequence of independently verifiable vertical slices that satisfies accepted requirements, or challenge an existing plan before it is executed; implementation follows the accepted scope and applicable stack skills.
Workflow
To write a plan, follow the steps below. To challenge an existing plan, read only plan-review; to settle an unfamiliar API or architecture choice first, read research-brief.
- Read the accepted scope: identify the outcome, constraints, authorization, and unresolved decisions; stop planning when material options still need a user decision.
- Inspect the implementation: verify relevant paths, interfaces, dependencies, tests, and current work; preserve user changes and reuse existing mechanisms.
- Choose useful slices: order the smallest independently verifiable changes by dependency; identify shared files and real compatibility or migration risks.
- Specify proof: each slice names its outcome, affected files, dependencies, implementation steps, focused checks with expected results, and objective acceptance criteria. Record decisions (signatures, files, test names and assertions, spec values), not implementation bodies; write code only where an algorithm would otherwise be ambiguous.
- Review the plan: map every requirement to a slice, verify unfamiliar APIs, remove speculative flexibility, and state any decision that truly blocks execution. Name the input classes or failure modes the requirements imply but no slice tests, and add each test to its owning slice.
- Deliver at the right scale: use a compact task table for linear work; add interface contracts, concurrency, rollout, or rollback details where needed, retaining every applicable risk and proof boundary. A plan much longer than its requirements is transcribing the program; replace bodies with signatures and assertions.
- Hand off: identify the first executable slice and the full project gate.
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.
- 12d ago Changed · +3 tokens per session bdf7193cafd0
- 14d ago Changed e9063f67eaba
- 15d ago Changed · -14 tokens per session 89701d306545
- 29d ago Changed · +11 lines · +14 tokens per session e2dfc3f88fdf
- 1mo ago Changed · +1 lines · -15 tokens per session 0a883fa7b0a6
- 1mo ago Changed 1df79602fbf3
- 1mo ago Changed · -16 lines · -12 tokens per session 620767c949ea
- 1mo ago First seen · 52 lines · 42 tokens per session scan A 10efbaad9ec2
implementation-plan is a skill published in the GitHub repository fmind/dot (12 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 900 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.