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/phobologic/claude_code_helpers/reviewnpx skills add phobologic/claude_code_helpers --skill reviewgit clone --depth 1 https://github.com/phobologic/claude_code_helpersWhat 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.00035 | $0.00391 |
| Opus 5 | $0.00017 | $0.00196 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
review 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 orchestrating a fast pre-merge code review. A dedicated adversarial sub-agent does the actual reviewing so it brings a fresh, unbiased perspective.
Step 1: Collect context
Run:
review-setup
Capture TK_AVAILABLE, REVIEW_CMD, and FILES_COUNT from the output. Also generate a session tag: SESSION_TAG=review-$(date +%Y%m%d-%H%M).
Step 2: Guard
If FILES_COUNT is 0, tell the user there are no uncommitted changes to review and stop.
Step 3: Launch the code-critic sub-agent
Use the Task tool to invoke the code-critic sub-agent. Pass REVIEW_CMD, and tk parameters when available.
tk mode (TK_AVAILABLE=true)
Task: Adversarial code review
Prompt: TK_MODE=true SESSION_TAG=<session_tag> REVIEW_CMD=<review_cmd> Review ONLY the files listed in .code-review/changed-files.txt and nothing else
SubagentType: code-critic
non-tk mode (TK_AVAILABLE=false)
Task: Adversarial code review
Prompt: REVIEW_CMD=<review_cmd> Review ONLY the files listed in .code-review/changed-files.txt and nothing else
SubagentType: code-critic
Step 4: Present results
The critic's output is the review. Display it.
In tk mode, additionally tell the user:
- The session tag used:
<session_tag> - How to find all tickets from this review:
tk query '.tags | contains(["<session_tag>"])'
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 · 50 lines · 35 tokens per session scan A 8b810f766f13
review is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 391 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
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…