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/xbim08/awesome-claude-code-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/xbim08/awesome-claude-code-plugins/fix-pr)<a href="https://agentmods.dev/commands/xbim08/awesome-claude-code-plugins/fix-pr"><img src="https://agentmods.dev/badge/commands/xbim08/awesome-claude-code-plugins/fix-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.1 | $0.00028 | $0.00068 |
| Opus 5 | $0.00014 | $0.00034 |
| Sonnet 5 | $0.00006 | $0.00014 |
| Haiku 4.5 | $0.00003 | $0.00007 |
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 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
Fetch unresolved comments for this branch's PR, then fix them
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 · 8 lines · 28 tokens per session scan A d4a3b5dcd2e2
fix-pr is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 68 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
claudex
Claude writes, Codex reviews, iterate until both agree — then ship with love.
verdict
Two-model verdict — Claude and Codex independently review the same diff, disagreements surfaced.
code-review
Perform a comprehensive code review of recent changes.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
stats
Agreement stats — how often do Claude and Codex actually agree in this repo?
setup
Verify ClauDex prerequisites — Codex CLI, authentication, and git.