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.
git 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/fix-pr)<a href="https://agentmods.dev/commands/jeffh/claude-plugins/fix-pr"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/fix-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jeffh/claude-plugins/fix-pr"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/fix-pr.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.01044 |
| Opus 5.5 | $0.00006 | $0.00418 |
| Sonnet 5.5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
fix-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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix PR
You are tasked with fixing issues on a Pull Request based on review feedback, status checks, and CI failures.
Input
The user will provide either:
- A PR number (e.g.,
123) - A PR URL (e.g.,
https://github.com/owner/repo/pull/123)
If just a number is provided, assume it's for the current repository.
Process
1. Gather PR Information
First, collect all relevant information about the PR:
# Get PR details (number, title, state, base branch)
gh pr view {PR} --json number,title,state,baseRefName,headRefName,body
# Get review comments (code review feedback)
gh api repos/{owner}/{repo}/pulls/{PR}/comments --jq '.[] | {path: .path, line: .line, body: .body, user: .user.login, created_at: .created_at}'
# Get PR review summaries (approved, changes requested, etc.)
gh api repos/{owner}/{repo}/pulls/{PR}/reviews --jq '.[] | {state: .state, body: .body, user: .user.login}'
# Get issue comments (general discussion on the PR)
gh api repos/{owner}/{repo}/issues/{PR}/comments --jq '.[] | {body: .body, user: .user.login, created_at: .created_at}'
# Get status checks
gh pr checks {PR} --json name,state,conclusion,description
# Get workflow run details for failed checks
gh run list --branch {head_branch} --limit 5 --json databaseId,name,conclusion,status
For failed workflow runs, get the logs:
gh run view {run_id} --log-failed
2. Analyze Feedback
Categorize all gathered feedback into:
- CI Failures: Failed status checks, workflow errors, test failures
- Review Comments: Code review feedback with specific file/line references
- Change Requests: Reviews marked as "changes requested" with specific asks
- General Comments: Discussion comments that may contain actionable feedback
- Unclear Feedback: Comments that don't have a clear action item
3. Create Task List
Use the TodoWrite tool to create a task list of all issues to fix. Each task should be specific and actionable:
- For CI failures: "Fix [test name] in [file]" or "Resolve [error type] in CI"
- For review comments: "Address review comment on [file:line] - [summary]"
- For change requests: "Implement requested change: [description]"
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.
- 1mo ago First seen · 134 lines · 14 tokens per session scan A 782fe7292e25
fix-pr is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 9d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,044 once invoked, about $0.0001 per session on Opus 5.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
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-tag
Create and push a version tag after a release PR has been merged.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.