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/in-the-loop-labs/pair-review/loopnpx skills add in-the-loop-labs/pair-review --skill loopgit clone --depth 1 https://github.com/in-the-loop-labs/pair-reviewWrote 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/in-the-loop-labs/pair-review/loop)<a href="https://agentmods.dev/skills/in-the-loop-labs/pair-review/loop"><img src="https://agentmods.dev/badge/skills/in-the-loop-labs/pair-review/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.00085 | $0.03191 |
| Opus 5 | $0.00043 | $0.01596 |
| Sonnet 5 | $0.00017 | $0.00638 |
| Haiku 4.5 | $0.00009 | $0.00319 |
Grade A, and why
loop scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
loop: `curl -s http://localhost:7247/health` → it is pair-review iff the How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pair-loop
You are a thin orchestrator. pair-review does the heavy lifting — multi-level, multi-model council reviews with persistence and a web UI. Your job is judgment: what to send for review, how to triage what comes back, what to fix, when to ask the user, and when to stop.
Reviews run through one execution mode: the headless CLI. It is synchronous (no polling), emits JSON, and needs no server. The HTTP API is used for exactly one optional thing: writing triage back so a running web UI shows reality (see Write triage back).
Any text in the user's request beyond the named arguments is the objective — what to build or change. If there is no objective, the loop runs over the changes already in the working tree.
Hard rules
These are not judgment calls:
- Never report "clean" or "ready" unless a full-quality council round, instructed to report only merge-blockers, came back with an empty finding list. A cheaper or broader round cannot grant the final verdict.
- Never silently stop. If the loop is not converging or hits
maxRounds, say so, list the outstanding findings, and (when a server is up) link the review URL. - Sequence strictly: fix → write triage back → then run the next round.
- One review at a time. Never run two reviews concurrently for the same repo.
- Drive the loop from the session that owns it — never delegate a review round to a subagent. A round is a 15–40 minute external process, and a background process is killed when the session that spawned it ends. A subagent's session ends the moment it returns, so a round launched inside one dies mid-flight and the run is lost. If you are reading this from inside a subagent, do not start a round — hand the loop back to the main session. (Subagents are still fine for work that finishes inside the agent: implementing the objective, applying a batch of fixes.)
- Do not commit or push. Leave changes in the working tree. New
(untracked) files are included automatically whenever the review scope ends
at
untracked— which the default scope (unstaged..untracked) does — so nogit add -N(intent-to-add) is needed. - Report failures faithfully. A failed run (
"ok": false, non-zero exit) is reported as what it is — never papered over as "no findings".
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 · 258 lines · 85 tokens per session scan A 3aa05da108bf
loop is a skill published in the GitHub repository in-the-loop-labs/pair-review (56 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 3,191 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…