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/fmind/dot/plan-executionnpx skills add fmind/dot --skill plan-executiongit 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/plan-execution)<a href="https://agentmods.dev/skills/fmind/dot/plan-execution"><img src="https://agentmods.dev/badge/skills/fmind/dot/plan-execution.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.00039 | $0.00993 |
| Opus 5 | $0.00019 | $0.00496 |
| Sonnet 5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
plan-execution 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 yesterday.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Execution
Turn an accepted plan into reviewable evidence slice by slice; implementation-plan writes the plan, and commit, push, deploy, and publication stay separate authorities.
Workflow
- Confirm authority: A plan alone is not authorization to mutate the repository; confirm the request includes implementation, then re-read the request, plan, repository instructions, and status before the first edit.
- Capture the baseline: Record branch,
HEAD, status, relevant test state, and known external boundaries. Preserve staged, unstaged, and untracked user work and note which edits belong to the user. - Reconcile the plan: Check that paths, symbols, dependency versions, commands, and assumptions still match the checkout; note deviations in the execution notes and ask for direction when the outcome would materially change.
- Order the work: Follow the dependency graph and critical path; take the smallest vertical slice that yields independently useful behavior and proof.
- Establish red evidence: Use test-driven-development for behavior changes, a characterization test for legacy behavior, or a failing validation signal for non-code changes.
- Implement minimally: Use the applicable stack skill and touch only files traceable to the current slice.
- Verify the slice: Run the focused test, formatter, static checks, and any bounded runtime or manual check the plan promised; read the full output.
- Review the delta: Compare the diff with the intended slice, remove only artifacts this work introduced, and use diff-review for risky changes.
- Checkpoint honestly: Mark a slice complete only with fresh evidence; record partial results, deviations, and residual gaps before moving on.
- Gate the candidate: Run the full gate (
mise run all); if the tree carries unrelated changes and the gate write-formats, run it in a temporarygit worktreeor fall back tomise run checkandmise run test(see mise). - Hand off: Summarize changes, verification, untested boundaries, and remaining tasks; report the highest proven rung of the proof ladder and leave the worktree for review.
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.
- yesterday First seen · 42 lines · 39 tokens per session scan A eb524c19de46
plan-execution is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 993 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
google-workspace-cli
Use gws across Workspace APIs with schema-first calls, profile isolation, bounded reads, and verified Drive, Docs, Sheets, Gmail, Calendar, or Chat writes.
handover
Write a self-contained follow-up prompt carrying this session's decisions, constraints, and verified findings into a fresh agent session. Use when handing unfinished work to a new context window.
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.
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.