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/martinemde/dotfiles/review-plannpx skills add martinemde/dotfiles --skill review-plangit clone --depth 1 https://github.com/martinemde/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/martinemde/dotfiles/review-plan)<a href="https://agentmods.dev/skills/martinemde/dotfiles/review-plan"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/review-plan.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.1 | $0.00000 | $0.00861 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
review-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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Plan: Validate Before Executing
You are reviewing an implementation plan. Your job is to find problems before they waste execution time. Be direct about issues — a false positive costs a re-read, a missed problem costs a rework cycle.
Arguments
$ARGUMENTS
Instructions
1. Find the Plan
Read the active plan file. Check these locations in order:
~/.claude/plans/— most recent.mdfile- Plan content in recent conversation context
If no plan is found, report this and stop.
2. Cross-Reference with Codebase
For every concrete claim the plan makes, verify it:
| Claim type | Verification |
|---|---|
"Modify src/foo.ts" |
Does src/foo.ts exist? |
"Call functionName()" |
Does functionName exist? Is the signature correct? |
"Import from package" |
Is package in dependencies? |
"Tests are in test/" |
Does the test directory exist? What patterns do existing tests follow? |
| "Convention is X" | Does CLAUDE.md or the codebase confirm this? |
Use Glob, Grep, and Read to verify. Don't trust the plan's claims about the codebase — check them.
3. Check Task Graph Integrity
Review the dependency structure:
- Missing dependencies: Does Task C use output from Task A without declaring
blockedBy: [A]? - Circular dependencies: Are there cycles that would deadlock execution?
- Over-serialization: Are tasks marked sequential that could actually run in parallel?
- Under-serialization: Are tasks marked parallel that actually depend on each other (e.g., both touch the same file)?
- Orphan tasks: Are there tasks with no downstream consumer? (Might be intentional, might be a gap.)
4. Assess Instruction Clarity
What ships with it
1 file 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.
- 6d ago First seen · 113 lines · 0 tokens per session scan A 15e82c50d25c
review-plan is a skill published in the GitHub repository martinemde/dotfiles (9 stars, last pushed 6d ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 861 tokens. 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…
neovim-configuration
Modern Neovim configuration expertise including Lua scripting, plugin management with lazy.nvim, LSP setup with Mason, AI integration with claudecode.nvim/opencode.nvim, and workflow optimization. Covers keymaps, autocommands, and treesitter configuration. Use when user mentions Neovim, nvim, lazy.nvim, Mason…