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 d-oit/rust-2026-template --skill reviewing-pull-requestsgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/reviewing-pull-requests)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/reviewing-pull-requests"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/reviewing-pull-requests/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/d-oit/rust-2026-template/reviewing-pull-requests"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/reviewing-pull-requests.svg" alt="Reviewed on agentmods" width="80" 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.00132 | $0.02933 |
| Opus 5.5 | $0.00053 | $0.01173 |
| Sonnet 5.5 | $0.00026 | $0.00587 |
| Haiku 4.5 | $0.00013 | $0.00293 |
Grade A, and why
reviewing-pull-requests scanned grade A with 1 finding 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 20d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl` — you would lose the credential scoping that keeps writes auditable. How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your knowledge of this repository's conventions, its GitHub state, and what a given diff actually does is unreliable. Prefer retrieval over pre-training. Read the PR body, the full files, the prior comments, and the check runs before asserting anything about a change.
Principles
- Evidence or nothing. A finding without a
path:lineand a verifiable reason is dropped, not softened. - Precision over recall. A missed finding costs far less than a wrong one. Engineers forgive a tool that misses something; they abandon one that cries wolf.
- Close, never delete. Closing is reversible with a comment; deletion is not.
- Never post unvetted. Draft everything; a human submits every comment,
verdict, and close. Never send
--approveor--request-changesunprompted. - Staleness is not impact. Age alone never justifies closing.
Prerequisites
gh auth status || exit 1
gh repo view --json defaultBranchRef >/dev/null || exit 1
If gh is missing or unauthenticated, stop and report it. Do not fall back to
curl — you would lose the credential scoping that keeps writes auditable.
Decision Rule: Review Or Close
Impact is blast radius, not diff size. A 2,000-line lockfile bump is low impact; a 3-line change to an auth check is high impact.
| Signal | Low impact | Needs review |
|---|---|---|
| Touches public API surface, auth/crypto, permission checks, non-additive schema/migrations, build/release/CI config | no | yes |
mergeStateStatus |
UNBLOCKED |
DIRTY |
reviewDecision |
not CHANGES_REQUESTED |
CHANGES_REQUESTED |
| Required checks | all SUCCESS or SKIPPED |
any failing or pending |
authorAssociation / maintainerCanModify |
MEMBER/OWNER/COLLABORATOR, or maintainerCanModify: true |
FIRST_TIME_CONTRIBUTOR and false |
isDraft |
false | true (skip drafts entirely) |
Diff is already in the base branch (git diff base...head empty) |
yes | — |
| Pure docs/formatting/lockfile/generated churn | yes | — |
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.
- 20d ago First seen · 251 lines · 132 tokens per session scan A 7544fbdb8e3e
reviewing-pull-requests is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed today), licensed MIT. It adds 132 tokens to every session and 2,933 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-27.
Other skills, from other repositories
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.