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/mitodl/agent-kit/code-reviewnpx skills add mitodl/agent-kit --skill code-reviewgit clone --depth 1 https://github.com/mitodl/agent-kitWhat 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.00148 | $0.01908 |
| Opus 5 | $0.00074 | $0.00954 |
| Sonnet 5 | $0.00030 | $0.00382 |
| Haiku 4.5 | $0.00015 | $0.00191 |
Grade A, and why
code-review 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 yesterday.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Reviews a diff against four dimensions — correctness, simplification, efficiency, reuse — and reports findings as a severity-ordered table. Every finding is re-checked against the actual code before it ships, so the report doesn't carry a pattern-matched guess dressed up as a bug.
See references/dimensions.md for the four dimensions with worked examples of a real finding vs. a non-finding. See references/findings-format.md for the table schema and a full worked example.
Scope input
Resolve what to review from the request, in this order:
- No target given — combine three sources:
git diff(unstaged, tracked changes),git diff --staged, and untracked files. Plaingit diff/git diff --stagednever show untracked files — a working tree containing only a brand-new file looks empty to both — so checkgit status --porcelainfor??entries and include them (git add -N <file>first makes each show up as an addition in the plaingit diffwithout staging its content). Only fall back togit diff HEAD~1when all three are empty, and say explicitly that's what's being reviewed instead of silently reporting nothing. - A branch name — diff against where it forked from the default
branch, not a plain two-dot diff: detect the default branch via
git symbolic-ref refs/remotes/origin/HEAD. That ref only exists once a remote's HEAD has been set (git cloneusually does this, but a fresh/local-only repo or an unset remote won't have it — verified: a baregit initwith no remote raises "not a symbolic ref"); when it's missing, fall back togh repo view --json defaultBranchRef --jq .defaultBranchRef.nameifghand a GitHub remote are available, otherwise ask the user which branch to diff against rather than guessingmainormaster. However the default branch was found, find the merge base (git merge-base <default> <branch>), thengit diff <merge-base>...<branch>. - A path —
git diff HEAD -- <path>(covers staged and unstaged changes to the path in one call — plaingit diff -- <path>shows only unstaged, so a fully-staged change at that path would otherwise look like an empty diff), plus the same untracked-file handling as rule 1, scoped to that path. Same default-branch detection as rule 2 if a branch was also named. - A PR number — when
ghis available and the repo has a GitHub remote,gh pr diff <number>.
What ships with it
2 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.
- yesterday First seen · 166 lines · 148 tokens per session scan A 6a4cb10a8ee8
code-review is a skill published in the GitHub repository mitodl/agent-kit (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 148 tokens to every session and 1,908 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.
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…