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/band-app/band/review-changesnpx skills add band-app/band --skill review-changesgit clone --depth 1 https://github.com/band-app/bandWrote 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/band-app/band/review-changes)<a href="https://agentmods.dev/skills/band-app/band/review-changes"><img src="https://agentmods.dev/badge/skills/band-app/band/review-changes.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.00136 | $0.02538 |
| Opus 5 | $0.00068 | $0.01269 |
| Sonnet 5 | $0.00027 | $0.00508 |
| Haiku 4.5 | $0.00014 | $0.00254 |
Grade A, and why
review-changes 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 5d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Changes
This skill orchestrates Band's four-specialist PR review. It is read-only — the caller decides what to do with the output.
You are the orchestrator. Your job is to:
- Gather context (changed files, linked issues, PR details, repo conventions).
- Dispatch four specialist sub-reviewers in parallel with that context bundle.
- Aggregate findings per section (one section per specialist).
- Emit a single overall Verdict line (
approved 👍if no blocker anywhere, elserequest changes 👎).
You never modify files yourself. You never paraphrase findings. You never compose findings — the specialists do; you orchestrate and aggregate.
Specialists
| Specialist | Criteria | Scope |
|---|---|---|
coding-reviewer |
.claude/coding-criteria.md (CODE-1…CODE-19) |
production source code |
testing-reviewer |
.claude/testing-criteria.md (TEST-1…TEST-35) |
tests, fixtures, page objects |
security-reviewer |
.claude/security-criteria.md (SEC-1…SEC-15) |
source, tests, config, scripts |
performance-reviewer |
.claude/performance-criteria.md (PERF-1…PERF-10) |
production source, hot paths |
Each specialist also applies cross-cutting concerns (correctness, pattern drift) inside its scope, tagged correctness: / pattern: instead of a rule ID. Specialists do not compose the Verdict — that's your job.
Step 1 — Gather context
The caller supplies, at minimum, REPO and one of (PR NUMBER) or (BASE + HEAD refs).
Diff
- Open PR:
gh pr diff <num>for the diff;gh pr view <num> --json title,body,headRefName,baseRefNamefor metadata. - No PR yet (local pre-push):
git diff <base>...<head>(three-dot form — matches what GitHub will show on a future PR);git log <base>..<head> --format='%h %s%n%b'for commit history.
Do not truncate.
Linked issues
Look for, in order:
closes #<n>/fixes #<n>/resolves #<n>in PR body or commit messages.- A leading number in the branch name (
123-fix-foo→ issue 123).
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.
- 5d ago First seen · 208 lines · 136 tokens per session scan A b44632eb2d8e
review-changes is a skill published in the GitHub repository band-app/band (5 stars, last pushed yesterday), licensed MIT. It adds 136 tokens to every session and 2,538 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…