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/webjsdev/webjs/pr-reviewnpx skills add webjsdev/webjs --skill pr-reviewgit clone --depth 1 https://github.com/webjsdev/webjsWhat 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.00075 | $0.01955 |
| Opus 5 | $0.00037 | $0.00978 |
| Sonnet 5 | $0.00015 | $0.00391 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
pr-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a pull request (inline, posted via the GitHub API)
Review a PR like a human reviewer who happens to use the GitHub API instead of the dashboard. Same output a person would produce on github.com: one submitted review carrying a summary and inline comments anchored to the exact lines, with GitHub suggestion blocks where the fix is concrete enough to spell out.
This skill is agent-agnostic on purpose. Everything below is plain gh
CLI (or raw REST with any HTTP client and a token), no harness-specific
tools, so it works the same from any agent or harness that can run shell
commands.
The contract (read first, all four are hard rules)
- Inline. The agent that received the ask performs the review itself, in the same session. Never spawn a reviewer subagent, a fleet, or a background task for it, and never run a multi-round review cycle. One read over the whole diff, one posted review, done.
- Review only. The reviewer never fixes what it finds: no commits, no pushes, no code edits, no resolving of threads. Findings are the deliverable. Fixing them is separate work for whoever owns the branch, on a separate ask.
- No CI. Never wait on, read, or report CI or check status. Checks are the merge gate's business, not the reviewer's, and a review that stalls on a pending check has failed its one job of being fast feedback on the code.
- Read-only on git. Reviewing needs no checkout. Do not run any
git command that changes branch, HEAD, the index, or the working
tree (
checkout,switch,reset,restore,stash,merge,rebase,clean). Read-only inspection (git log,git show,git diff,git status,git blame) is fine.
Steps
1. Resolve the PR
An explicit #N wins. Otherwise resolve the current branch's open PR
over REST (owner/repo from the git remote):
BRANCH=$(git branch --show-current)
gh api "repos/<owner>/<repo>/pulls?head=<owner>:$BRANCH&state=open" \
--jq '.[0].number'
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 · 174 lines · 75 tokens per session scan A 08d1da168d28
pr-review is a skill published in the GitHub repository webjsdev/webjs (109 stars, last pushed 11d ago), licensed MIT. It adds 75 tokens to every session and 1,955 once invoked, about $0.0004 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
javascriptcore-garbage-collector
JSC GC reference for Bun. Use for use-after-free, JS object leaks, "collected too early", or when touching WriteBarrier, visitChildren, visitAdditionalChildren, JSRef, JSC::Strong/Weak, hasPendingActivity, ensureStillAlive, addOpaqueRoot, reportExtraMemoryAllocated, IsoSubspace, HeapAnalyzer, finalize.
implementing-jsc-classes-cpp
Implements JavaScript classes in C++ using JavaScriptCore. Use when creating new JS classes with C++ bindings, prototypes, or constructors.
implementing-jsc-classes-rust
Creates JavaScript classes using Bun's Rust bindings generator (.classes.ts). Use when implementing new JS APIs in Rust with JSC integration, prototypes, or constructors.
rust-system-calls
Guides using bunsys for system calls and file I/O in Rust. Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc.
slowest-tests
Find the top-N slowest test files in CI from a recent BuildKite run, optionally posting the results to a Slack channel as a formatted table. Use when asked to find slow CI tests, "what's making CI slow", or to post a slow-test report to Slack.
writing-bundler-tests
Guides writing bundler tests using itBundled/expectBundled in test/bundler/. Use when creating or modifying bundler, transpiler, or code transformation tests.