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/juanmhidalgo/claude-plugins/prgit clone --depth 1 https://github.com/juanmhidalgo/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/juanmhidalgo/claude-plugins/pr)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/pr"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/pr.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.00034 | $0.01424 |
| Opus 5 | $0.00017 | $0.00712 |
| Sonnet 5 | $0.00007 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
pr 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Code Review
Target PR: $ARGUMENTS
Repository: !git remote get-url origin
Current branch: !git branch --show-current
Execute this multi-step code review workflow precisely:
Step 1: Eligibility Check
Use Agent tool with subagent_type="code-review:pr-eligibility-checker" and model="haiku" to check if the PR is eligible for review.
Stop conditions (do not proceed if any are true):
- PR is closed or merged
- PR is a draft
- PR author is a bot (dependabot, renovate, github-actions)
- PR is trivial (only docs/config/lockfiles)
- PR already has a Claude Code review comment
If not eligible, inform the user why and stop.
Step 2: CLAUDE.md Discovery
Use Glob to find CLAUDE.md files: **/CLAUDE.md
Read each one found. Focus on rules relevant to the changed files.
Step 3: PR Summary
Use Agent tool with subagent_type="code-review:pr-summarizer" and model="haiku" to get a summary of the PR changes.
Store this summary for context in the parallel reviews.
Step 4: Parallel Code Review (5 Agents)
Launch these 5 agents in parallel using multiple Agent tool calls in a single message:
-
CLAUDE.md Compliance -
subagent_type="code-review:claudemd-compliance-reviewer"(Sonnet)- Provide: PR number, CLAUDE.md files from Step 2, PR summary
-
Bug Scanner -
subagent_type="code-review:bug-scanner"(Sonnet)- Provide: PR number
-
Git History -
subagent_type="code-review:git-history-reviewer"(Sonnet)- Provide: PR number, files changed
-
Previous PR Comments -
subagent_type="code-review:pr-comments-reviewer"(Sonnet)- Provide: PR number, files changed
-
Code Comments -
subagent_type="code-review:code-comments-reviewer"(Sonnet)- Provide: PR number, files changed
Collect all issues from all agents.
Step 5: Confidence Scoring
For each issue found in Step 4, launch a parallel Haiku agent using Agent tool with subagent_type="code-review:confidence-scorer" and model="haiku".
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 · 196 lines · 34 tokens per session scan A 45f1c8bb400c
pr is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 1,424 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 commands, from other repositories
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
lavra-import
Import a markdown plan into beads as an epic with child tasks.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
youtube-pulse
Summarize latest videos from tracked YouTube channels and extract short-term investment signals relevant to current holdings. Run after /market-pulse for context, or standalone for a quick opinion check.