Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yorrick/agent-skills/plugin install dev-loopWrote 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/yorrick/agent-skills/review-loop)<a href="https://agentmods.dev/commands/yorrick/agent-skills/review-loop"><img src="https://agentmods.dev/badge/commands/yorrick/agent-skills/review-loop/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/yorrick/agent-skills/review-loop"><img src="https://agentmods.dev/badge/commands/yorrick/agent-skills/review-loop.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.00023 | $0.00260 |
| Opus 5.5 | $0.00009 | $0.00104 |
| Sonnet 5.5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
review-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 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.
What it actually says
Review Loop
Run the review loop on an existing PR. This skips brainstorming and implementation — it goes straight to the iterative review cycle.
Execute the dev-loop script with the --review-only flag using the Bash tool:
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/dev-loop.py" $ARGUMENTS
The script will:
- Run /simplify and commit fixes
- Run /code-review:code-review + /security-review in parallel
- Wait for CI/CD checks to complete (if any exist)
- If Critical/Important issues or CI failures found: fix (including re-running smoke test validation from the plan) and loop
- If clean and CI passing: done
Monitor progress from another terminal:
- Status:
watch -n1 cat .dev-loop/latest/status.txt - Full log:
tail -f .dev-loop/latest/dev-loop.log
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 · 25 lines · 23 tokens per session scan A 29e048396ef9
review-loop is a command published in the GitHub repository yorrick/agent-skills (11 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 260 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-31.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).