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 skills add NYTC69/review-loop --skill review-prgit clone --depth 1 https://github.com/NYTC69/review-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/skills/nytc69/review-loop/review-pr)<a href="https://agentmods.dev/skills/nytc69/review-loop/review-pr"><img src="https://agentmods.dev/badge/skills/nytc69/review-loop/review-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.00043 | $0.02493 |
| Opus 5 | $0.00022 | $0.01247 |
| Sonnet 5 | $0.00009 | $0.00499 |
| Haiku 4.5 | $0.00004 | $0.00249 |
Grade A, and why
review-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 8d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Code Review
Run a comprehensive code review using multiple specialized agents, each focusing on a different aspect of code quality. Agents are invoked via the Agent tool and run with read-only access to the project (except code-simplifier which needs write access).
Review Aspects (optional): "$ARGUMENTS"
Step 1 — Determine Review Scope
- Run
git diff --name-onlyto identify unstaged changed files (this is the default scope). If there are no unstaged changes, fall back togit diff --cached --name-only(staged changes). - If no changes are found at all, tell the user and stop.
- Parse
$ARGUMENTSto detect:- Aspect selection: one or more of
code,errors,comments,types,tests,simplify,all. Default:all. - Execution mode:
parallelkeyword triggers parallel mode. Default: sequential.
- Aspect selection: one or more of
- Run
git diff(orgit diff --cached) to capture the full diff content — this is what agents will review.
Display to the user:
── review-pr ──────────────────────────────────────
Scope: git diff (unstaged changes)
Files: {N} changed
Aspects: {selected aspects or "all"}
Mode: {sequential | parallel}
────────────────────────────────────────────────────
Step 1.5 — Load shared tier config
Read .review-loop/config.md if it exists. Extract:
judgment_model: shared tier override for judgment-tier review agentscheap_model: shared tier override for cheap-tier review agents; if absent, cheap-tier dispatches backstop toclaude-haiku-4-5-20251001review_style: optional review tone / cross-cutting rules
Missing agent tier defaults to judgment.
Step 2 — Available Review Aspects
Each aspect maps to a specialized agent in the agents/ directory:
| Aspect | Agent | When applicable |
|---|---|---|
| code | code-reviewer | Always (general code quality) |
| errors | silent-failure-hunter | Always (error handling analysis) |
| comments | comment-analyzer | If comments/docs added or changed |
| types | type-design-analyzer | If types added or modified |
| tests | pr-test-analyzer | Always (checks if changes lack tests too) |
| simplify | code-simplifier | After other reviews pass (polish) |
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.
- 8d ago First seen · 298 lines · 43 tokens per session scan A 027cf5fc9ae4
review-pr is a skill published in the GitHub repository NYTC69/review-loop (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,493 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 skills, from other repositories
ship-it-or-fix-it
Oracle-frozen Builder and independent-Judge convergence cycle. Load ONLY when the operator explicitly sets Governance Dial G2 for the task, or explicitly names this skill or an active work unit already running it. Never auto-activate on task class, such as security, auth, or payments. If a task seems to warrant G2 and…
test-verification
Requires behavioral, failure-path, and durable-seam evidence for tests and review. Use when writing tests, reviewing test coverage, assessing behavioral test quality, or accepting high-risk behavior on test evidence.
spec-brainstorm
Conversational design workshop for substantial work. Interviews the human one question at a time, explores 2-3 approaches with trade-offs, and presents the design section by section for approval before writing only design.md, then stops. Combines requirements discovery with codebase research and architecture design.…
spec-plan
Write approved implementation plans in one of two modes. Explicit Inline mode creates a conversational plan for bounded work. Spec-backed Plan converts an approved design.md into plan.json. Both modes stop after producing their plan output. Trigger after atelier-orchestrator selects a mode, when the user asks to plan…
atelier-orchestrator
Skill routing and workflow orchestration. Selects Inline Plan or Spec-backed Plan, routes to the correct workflow skill, and manages transitions between phases. Use when starting any conversation or task to determine which planning mode and skill apply.
oracle-debug
Disciplined debugging methodology. Triggers on bug reports, test failures, "debug this", "diagnose this", unexpected behavior, build failures, integration issues, or performance regressions. Find root cause before a permanent corrective fix; contain urgent harm safely first.