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/dotfiles/implementation-plannpx skills add fmind/dotfiles --skill implementation-plangit clone --depth 1 https://github.com/fmind/dotfilesWhat 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.00042 | $0.01153 |
| Opus 5 | $0.00021 | $0.00576 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00115 |
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 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 — 52 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 the accepted intent.
Authority Boundary
Planning is read-only by default. Do not edit source, create issues, install dependencies, commit, push, deploy, or publish while producing a plan unless the user explicitly requested that action.
Workflow
- Read the contract: Re-read the accepted spec or request. Extract requirements, non-goals, constraints, success criteria, authority limits, and unresolved decisions.
- Inspect reality: Read repository instructions, status, relevant source, tests, manifests, task definitions, recent history, and existing patterns. Preserve staged, unstaged, and untracked user work.
- Verify APIs: Confirm installed dependency versions and read their exact local source plus current authoritative documentation before planning against an unfamiliar API.
- Map the change: Describe the current flow, desired flow, affected components, interfaces, data, trust boundaries, and operational consumers. Record existing code to reuse or delete.
- Compare real options: For a meaningful architectural or tooling choice, present two or three numbered options with complexity, maintenance, security, reversibility, and migration trade-offs. Recommend the simplest adequate option.
- Lock boundaries: Assign each file or package one responsibility. Prefer deep modules that hide decisions over pass-through layers, put tests and callers across the same real seam, and delay a generalized adapter until more than one concrete variation proves it. Record interface signatures, ownership, invariants, domain vocabulary, and compatibility behavior shared across tasks.
- Slice vertically: Order work by dependencies so each slice delivers a coherent behavior through its test boundary. Fold scaffolding, configuration, documentation, and telemetry into the slice that needs them.
- Design proof first: For each slice, name the failing or characterization test, focused command, full project gate, runtime/manual evidence, and expected failure or success signal.
- Plan safe change: Cover data or schema migration, backward compatibility, feature flags, observability, rollout, rollback, support, and cleanup only when applicable.
- Mark concurrency: Parallelize only independent tasks with disjoint ownership. Name shared files, generated outputs, runtime leases, and merge order explicitly.
- Self-review: Map every requirement to a task and proof, remove placeholders and speculative flexibility, verify paths and symbols, and identify anything that still requires a user decision. Apply the deletion test: an abstraction earns its place only when removing it would spread meaningful complexity or violate a real seam.
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 · 52 lines · 42 tokens per session scan A c35a0f885bba
implementation-plan is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,153 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-08-31.
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…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…