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/timothywarner-org/claude-code/review-changesnpx skills add timothywarner-org/claude-code --skill review-changesgit clone --depth 1 https://github.com/timothywarner-org/claude-codeWhat 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.00094 | $0.00519 |
| Opus 5 | $0.00047 | $0.00260 |
| Sonnet 5 | $0.00019 | $0.00104 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
review-changes 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
Review uncommitted changes
The current diff, status, and recent history are inlined below. Read them before responding.
Working tree diff
git diff HEAD
Index + working tree status
git status --short
Last 5 commits (for tone and style reference)
git log -5 --oneline
Your task
Review the changes above. Flag bugs, anti-patterns, missing tests, and any violation of this repo's voice rules. Be terse, be honest, no glazing.
Hard checks (block-on-find)
- No em dashes. Hyphens with spaces, commas, or periods only.
- Never use "ask" as a noun. "A heavy ask" is a rewrite.
- No AWS references. Not in code, not in comments, not in docs.
- No hardcoded secrets. Flag any string that looks like an API key, token, or password.
- No
console.login shipped JS/TS. Test files and demos insegment_*/are fine.
Soft checks (note, don't block)
- Comments explain WHY, not WHAT. Code shows what; comments justify design.
- PowerShell-first for shell scripts. Bash is the fallback.
- Azure-first for cloud examples. Never compare to other clouds.
- Docstrings/JSDoc on every new function or PowerShell script.
- Idempotent re-runs where state mutation is involved.
Report format
## Blockers
- file:line - issue - proposed fix
## Soft findings
- file:line - note
## What's working
- one or two things the diff got right (keep it brief, no glazing)
If the diff is empty, say so and stop. Do not invent findings.
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 · 63 lines · 94 tokens per session scan A 06649877c8ed
review-changes is a skill published in the GitHub repository timothywarner-org/claude-code (223 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 519 once invoked, about $0.0005 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…