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 skills add bjcoombs/ai-native-toolkit --skill pr-review-mergegit clone --depth 1 https://github.com/bjcoombs/ai-native-toolkitWrote 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/bjcoombs/ai-native-toolkit/pr-review-merge)<a href="https://agentmods.dev/skills/bjcoombs/ai-native-toolkit/pr-review-merge"><img src="https://agentmods.dev/badge/skills/bjcoombs/ai-native-toolkit/pr-review-merge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bjcoombs/ai-native-toolkit/pr-review-merge"><img src="https://agentmods.dev/badge/skills/bjcoombs/ai-native-toolkit/pr-review-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00123 | $0.03220 |
| Opus 5 | $0.00062 | $0.01610 |
| Sonnet 5 | $0.00025 | $0.00644 |
| Haiku 4.5 | $0.00012 | $0.00322 |
Grade A, and why
pr-review-merge 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 10d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review-to-Green + Smart Merge
Source-agnostic. Consumers pass: PR number, base branch, and bot-reviewer/CI rules
from the project's ## Marathon Configuration (defaults if absent).
Run-completion is gated elsewhere (floor)
This skill takes one PR to merge — a process signal. A green, merged PR is not proof the run's assembled product works, and this skill never certifies run-completion. That is gated by the acceptance-contract scripts the marathon engine invokes, not here: scripts/contract/start_gate.py fails closed at run start unless the contract is frozen before decomposition, scripts/contract/spawn_verifier.py is the sole custody chokepoint that spawns the cold non-implementing verifier against the assembled product, and scripts/contract/complete_gate.py fails closed unless that verifier's completion record validates. Merging here never substitutes for those gates. This note is part of the constitutional floor (FLOOR.md); the retro may propose changes but never self-apply them.
Ready Criteria (ALL must be true)
The PR is merge-ready only when all five are simultaneously true. Re-check from the top after every push — a fix can reopen an earlier criterion.
- Branch in sync — no merge conflicts with base branch
- CI passing — all checks succeed (or skipped)
- All inline comments addressed — see thread resolution rules
- No unaddressed conversation comments — actionable feedback responded to
- All review threads resolved — no unresolved threads remain
Thread resolution rules: Follow bot reviewer rules from the project's CLAUDE.md Marathon Configuration. Generic defaults:
- Bot threads: Fix the code and push. Resolve via GraphQL if addressed. Use jq JSON builder (avoids zsh
$escaping):jq -n --arg tid "$THREAD_ID" '{"query": "mutation { resolveReviewThread(input: {threadId: \"\($tid)\"}) { thread { isResolved } } }"}' | gh api graphql --input - - Human threads: Fix the code, reply inline explaining the fix,
@mentionthe reviewer. Do NOT resolve human threads — let the reviewer confirm.
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.
- 10d ago First seen · 221 lines · 123 tokens per session scan A ff6c86866dd1
pr-review-merge is a skill published in the GitHub repository bjcoombs/ai-native-toolkit (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 123 tokens to every session and 3,220 once invoked, about $0.0006 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
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
pr-describe
Write a pull-request title and body from the current branch's commits and diff against the base branch. Invoke when the user asks to open a PR, draft a PR description, or summarize a branch.
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.
pr-workflow
How to open a pull request that gets reviewed, and how to review one properly. Use when opening, describing, reviewing, updating or merging a PR.
github
GitHub source control and collaboration platform - lets an agent read pull requests, commits, repository metadata, and CI workflow results to support engineering review and documentation.