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/ciscodevnet/essentials/pr-reviewnpx skills add CiscoDevNet/essentials --skill pr-reviewgit clone --depth 1 https://github.com/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/pr-review)<a href="https://agentmods.dev/skills/ciscodevnet/essentials/pr-review"><img src="https://agentmods.dev/badge/skills/ciscodevnet/essentials/pr-review.svg" alt="Measured on agentmods" 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.00121 | $0.02807 |
| Opus 5 | $0.00060 | $0.01404 |
| Sonnet 5 | $0.00024 | $0.00561 |
| Haiku 4.5 | $0.00012 | $0.00281 |
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 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
Review one or more GitHub Pull Requests. Linters find, the LLM judges: a scan script runs the repo's own linters over each PR diff and emits a compact report, so you spend attention on correctness, cross-file logic, and disable-comment justification — not on re-deriving lint findings token by token.
This skill is variadic: it always operates on a set of PRs of size N ≥ 1. A single PR is just N = 1 and uses a fast in-place path; multiple PRs each get an isolated read-only worktree. Nothing is posted to any PR until you approve at one gate.
Phase: Review
Quick start
/pr-review https://github.com/<owner>/<repo>/pull/456 # one PR
/pr-review 456 # one PR, bare number
/pr-review 456 461 470 # several PRs
/pr-review # discover: PRs awaiting my review
Prerequisites
- GitHub CLI (
gh) — authenticated, with access to the repo. Primary integration. - The current directory must be a git repo (
.git/present). - Linters are optional: the scan runs whatever is installed (
ruff,pylint,bandit,eslint) and records the rest as "not run". In this repo Python linters run viauv. - TypeScript/eslint needs the workspace deps hoisted to the repo-root
node_modules— runnpm installonce at the repo root. Until then the scan records eslint as "not run" with that hint and continues. - For N > 1,
openssland (ideally)jqare used to create and provision isolated worktrees. GitHub MCP is an optional alternative for posting (see references/github-cli.md);ghis the default.
Workflow
1. Resolve the set of PRs
Build the list of PR numbers to review, then let N = its length.
- Refs given (one or many): each arg is a full URL
(
https://github.com/<owner>/<repo>/pull/<N>) or a bare number. Extractowner/repofrom URLs; for bare numbers usegh repo view --json nameWithOwner --jq .nameWithOwner. - No refs: discover PRs awaiting your review:
What ships with it
16 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.
- LICENSE 11 KB
- references/agent-conventions.md 2.0 KB
- references/batch-mechanics.md 5.7 KB
- references/deterministic-checks.md 3.3 KB
- references/github-cli.md 2.3 KB
- references/output-format.md 2.0 KB
- references/pylint-disables.md 2.9 KB
- scripts/create_review_worktree.sh 4.3 KB runs code
- scripts/find_review_requests.sh 2.9 KB runs code
- scripts/lib.sh 3.7 KB runs code
- scripts/lint_python.sh 3.9 KB runs code
- scripts/lint_ts.sh 5.2 KB runs code
- scripts/report.py 14 KB runs code
- scripts/scan_disables.sh 2.0 KB runs code
- scripts/scan-pr.sh 9.4 KB runs code
- scripts/test_report.py 7.9 KB runs code
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 · 243 lines · 121 tokens per session scan A d9b96137285c
pr-review is a skill published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 17d ago), licensed Apache-2.0. It adds 121 tokens to every session and 2,807 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-09-04.
Other skills, from other repositories
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
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.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…
understand-pr
Guided interactive PR review — understand the history and context before forming opinions.