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/dapi/claude-code-marketplace/pr-review-fix-loopnpx skills add dapi/claude-code-marketplace --skill pr-review-fix-loopgit clone --depth 1 https://github.com/dapi/claude-code-marketplaceWrote 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/skills/dapi/claude-code-marketplace/pr-review-fix-loop)<a href="https://agentmods.dev/skills/dapi/claude-code-marketplace/pr-review-fix-loop"><img src="https://agentmods.dev/badge/skills/dapi/claude-code-marketplace/pr-review-fix-loop.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.00382 | $0.01074 |
| Opus 5 | $0.00191 | $0.00537 |
| Sonnet 5 | $0.00076 | $0.00215 |
| Haiku 4.5 | $0.00038 | $0.00107 |
Grade A, and why
pr-review-fix-loop 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 4d 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.
PR Review Fix Loop
Navigator for iterative PR review + autofix loop. Analyzes context and suggests the optimal command.
When to activate
- User wants to review their PR changes
- User wants to fix review comments automatically
- User mentions "review loop", "autofix", "check PR"
- User wants Codex CLI review (standalone)
Instructions
Step 1: Determine user intent
Determine which command fits:
| Intent | Command |
|---|---|
| Iterative review + fix cycle | /pr-review-fix-loop |
| Standalone Codex review | /codex-pr-review |
| Just review without fixing | Suggest /pr-review-toolkit:review-pr instead |
If intent is unclear, ask the user.
Step 2: Suggest parameters (for /pr-review-fix-loop)
Based on context, suggest relevant flags:
- If user mentions specific aspects (code, errors, tests, types, comments, simplify) -- add
--aspects "..." - If user mentions criticality threshold -- add
--min-criticality N - If user mentions linting -- add
--lint - If user mentions Codex -- add
--codex - If user mentions specific base branch -- add
--base BRANCH - If user mentions iteration limit -- add
--max-iterations N
Default (no flags) is fine for most cases.
Step 3: Present the command
Show the user the suggested command with brief explanation:
/pr-review-fix-loop [flags]
Explain what will happen:
- PR review via pr-review-toolkit
- Automatic fix of issues above criticality threshold
- Repeat until clean or stagnation detected
- Report saved to
.claude/pr-review-loop-report.local.md
Step 4: Let user run the command
Do NOT run the command yourself. Present it and let the user invoke it.
Examples
Example 1: Simple PR review
User says: "review my PR"
Action: Suggest /pr-review-fix-loop
Result: User runs the command, loop starts
Example 2: Review with specific focus
User says: "check my PR for errors and code issues only"
Action: Suggest /pr-review-fix-loop --aspects "code errors"
Example 3: Review with Codex
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 134 lines · 382 tokens per session scan A d4419c6ac74f
pr-review-fix-loop is a skill published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 3d ago), licensed MIT. It adds 382 tokens to every session and 1,074 once invoked, about $0.0019 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 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…