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 commands/jeffh/claude-plugins/local_reviewgit clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/commands/jeffh/claude-plugins/local_review)<a href="https://agentmods.dev/commands/jeffh/claude-plugins/local_review"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/local_review.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 | $0.00009 | $0.00455 |
| Opus 5 | $0.00005 | $0.00228 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
local_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 3d 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
Local Review
You are tasked with setting up a local review environment for a colleague's branch. This involves creating a worktree, setting up dependencies, and launching a new Claude Code session.
Process
When invoked with a parameter like gh_username:branchName:
-
Parse the input:
- Extract GitHub username and branch name from the format
username:branchname - If no parameter provided, ask for it in the format:
gh_username:branchName
- Extract GitHub username and branch name from the format
-
Extract ticket information:
- Look for ticket numbers in the branch name (e.g.,
eng-1696,ENG-1696) - Use this to create a short worktree directory name
- If no ticket found, use a sanitized version of the branch name
- Look for ticket numbers in the branch name (e.g.,
-
Set up the remote and worktree:
- Check if the remote already exists using
git remote -v - If not, add it:
git remote add USERNAME [email protected]:USERNAME/humanlayer - Fetch from the remote:
git fetch USERNAME - Create worktree:
git worktree add -b BRANCHNAME ~/wt/humanlayer/SHORT_NAME USERNAME/BRANCHNAME
- Check if the remote already exists using
-
Configure the worktree:
- Copy Claude settings:
cp .claude/settings.local.json WORKTREE/.claude/ - Run setup:
make -C WORKTREE setup - Initialize thoughts:
cd WORKTREE && humanlayer thoughts init --directory humanlayer
- Copy Claude settings:
Error Handling
- If worktree already exists, inform the user they need to remove it first
- If remote fetch fails, check if the username/repo exists
- If setup fails, provide the error but continue with the launch
Example Usage
/local_review samdickson22:sam/eng-1696-hotkey-for-yolo-mode
This will:
- Add 'samdickson22' as a remote
- Create worktree at
~/wt/humanlayer/eng-1696 - Set up the environment
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.
- 3d ago First seen · 49 lines · 9 tokens per session scan A 8bf3baec3e8f
local_review is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 455 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.