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/jackfranklin/dotfiles/review-diffnpx skills add jackfranklin/dotfiles --skill review-diffgit clone --depth 1 https://github.com/jackfranklin/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.00034 | $0.00508 |
| Opus 5 | $0.00017 | $0.00254 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
review-diff 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 2d 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
You are presenting a git diff for human review using the ai-review CLI.
Steps
- Get the diff you want to review. For staged changes use
git diff --staged; for all uncommitted changes usegit diff HEAD; for a specific range usegit diff <base>..<head>. Note: Rungit add -N .first to include untracked files in the diff. This records the intent to add the files, making them visible togit diffwithout fully staging them. - Run the CLI, piping the diff to stdin:
Usegit diff HEAD | node ~/git/ai-review-plan/dist/cli.js diff --title "<short task-specific title>" --theme <dark|light>--theme lightunless the user has expressed a preference for dark mode. - Once the CLI launches, check its initial output (e.g.
Opening http://localhost:<port>) and tell the user what port the review is active on. Wait for the CLI to exit. It blocks until the user submits their review. - Check the exit code and stdout:
- Exit 0 (Approved): The user approved the diff. Address any inline comments in code, then proceed.
- Exit 1 (Changes Requested): The user requested changes. Do not commit or push. Show the user the comments from stdout, address them in code, and offer to run another review pass.
- The stdout always begins with
## Review: APPROVEDor## Review: CHANGES REQUESTED, followed by any comments as a numbered list. Read each comment carefully.
Notes
- Always pass
--title. Derive it from the branch name or the work being done (e.g. "Auth middleware changes", "Dark mode CSS") — never use a generic title like "Diff review". - Always pass
--theme. Default tolight; switch todarkif the user has indicated a preference. - If the diff is very large (hundreds of files), warn the user before opening and offer to scope it to specific paths:
git diff HEAD -- src/.
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.
- 2d ago First seen · 33 lines · 34 tokens per session scan A 9ae64568816f
review-diff is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 508 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.