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/jackfranklin/dotfiles/github-code-reviewnpx skills add jackfranklin/dotfiles --skill github-code-reviewgit clone --depth 1 https://github.com/jackfranklin/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.00056 | $0.01690 |
| Opus 5 | $0.00028 | $0.00845 |
| Sonnet 5 | $0.00011 | $0.00338 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
github-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 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Code Review
Review exactly one GitHub pull request. This skill supplies GitHub context and
an isolated checkout; code-review remains the governing implementation
review standard. Be direct and evidence-based. Do not praise, approve, post
GitHub comments, modify the active checkout, or run tests unless the user
separately asks.
Invocation
/github-code-review 42
Require one positive integer PR number. If it is missing or invalid, ask for it. Do not review every open PR as a fallback.
Workflow
1. Establish GitHub context
From the repository containing the active checkout, collect the PR metadata
and its patch. Use the explicit repository argument in later gh commands so
changing directories cannot change the target repository.
repo="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
gh pr view <number> -R "$repo" --json number,title,url,body,state,author,baseRefName,baseRefOid,headRefName,headRefOid,commits,files,additions,deletions,changedFiles,closingIssuesReferences,comments,reviews
gh pr diff <number> -R "$repo" --patch
Read the title and body before inspecting the implementation. Identify the claimed problem, expected outcome, scope, and any unstated assumptions. A missing or vague description is relevant context, but is not automatically a blocking finding.
2. Read linked issues
Use the structured closingIssuesReferences returned by the PR metadata. Read
every linked issue, including its title, body, state, labels, and comments:
gh issue view <issue-url> --json number,title,url,state,labels,body,comments
A closing reference is authoritative; do not guess linked issues by grepping
arbitrary #123 text in prose. If no issues are linked, report that limitation
rather than inventing one.
3. Read all prior PR feedback
Read all three categories of feedback:
- PR conversation comments (
commentsfromgh pr view); - submitted reviews and their bodies (
reviewsfromgh pr view); - inline review threads, including their resolved and outdated state.
What ships with it
1 file 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 · 194 lines · 56 tokens per session scan A c4176d4e332a
github-code-review is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 1,690 once invoked, about $0.0003 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…