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/ryanb/dotfiles/review-queuenpx skills add ryanb/dotfiles --skill review-queuegit clone --depth 1 https://github.com/ryanb/dotfilesWhat 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.00040 | $0.00394 |
| Opus 5 | $0.00020 | $0.00197 |
| Sonnet 5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
review-queue 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 2d 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 Queue
Show open pull requests that need review, ranked by how easy they are to review.
Run the pipeline:
~/.claude/skills/review-queue/pr-data.sh | ~/.claude/skills/review-queue/format-queue.sh
If this fails (e.g. not in a git repo, or gh not authenticated), report the error and stop.
The output is a pre-formatted ranked list. If the first line starts with PREFERENCES:, apply those instructions to the list — reorder, exclude, group, or highlight PRs as described. Re-number the final list sequentially. Preserve the same line format: N\. [title](url) (author) [+N, -N] with backtick-wrapped labels separated by commas and tree indentation using └─ / ├─ / │.
If there is no PREFERENCES: line, output the list as-is with no additional commentary.
A PR labeled other base is stacked on top of another branch, not the main branch. Never include an other base PR on its own — only show it nested under the PR for its base branch, as part of that stack. If applying preferences would exclude the base PR (or the base PR isn't in the queue), drop the other base PR too, since it can't be reviewed in isolation. Never re-parent an other base PR to a different branch to keep it in the list.
The line counts exclude test files, spec files, docs, and lock files.
What ships with it
3 files 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.
- 2d ago First seen · 28 lines · 40 tokens per session scan A c64e3ef52ea0
review-queue is a skill published in the GitHub repository ryanb/dotfiles (2,399 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 394 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…