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 jamestexas/agents --skill pr-reviewgit clone --depth 1 https://github.com/jamestexas/agentsWrote 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/jamestexas/agents/pr-review)<a href="https://agentmods.dev/skills/jamestexas/agents/pr-review"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/pr-review/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/jamestexas/agents/pr-review"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/pr-review.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.00043 | $0.08189 |
| Opus 5.5 | $0.00017 | $0.03276 |
| Sonnet 5.5 | $0.00009 | $0.01638 |
| Haiku 4.5 | $0.00004 | $0.00819 |
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 — 817 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review
Give or respond to pull request reviews. Review mode runs parallel analysis agents through three lenses — convention compliance, behavioral correctness, and infrastructure — then synthesizes findings with explicit disagreement handling.
Arguments
$ARGUMENTS
Arguments can be:
- PR number:
123orowner/repo#123 - Linear ticket:
ENG-123(finds associated PR) - Nothing (auto-detect from current branch)
- Explicit mode:
--review 123(give review) or--respond 123(address comments)
Phase 0: Structural Pre-flight
Runs before analysis agents. Output is local — not posted to GitHub.
0.1 Run review-prep
Invoke /review-prep $PR_NUM (or owner/repo#$PR_NUM if cross-repo).
Store the full ## Structural Pre-flight output as STRUCTURAL_CONTEXT.
0.2 Show reviewer
Display to the user now (before agents run):
- Both diagrams (spec-driven + emergent, or whichever are available)
- Drift analysis
- Insights block
- High blast-radius symbols list
Ask: "Structural pre-flight complete. Continue with full review?" If the user says no or wants to inspect further, stop here.
0.3 Handle unavailable
If review-prep returns status: unavailable:
- Note: "Structural analysis unavailable — mache could not index this repo. Proceeding with standard review."
- Set
STRUCTURAL_CONTEXT=""and continue to Phase 1. - Do NOT block the review.
Phase 1: Discovery
1.1 Determine the PR
If PR number provided:
PR_NUM="$1"
If Linear ticket ID provided (format: ABC-123):
# Use Linear MCP to get issue and extract PR link
If nothing provided, detect from current branch:
BRANCH=$(git branch --show-current)
gh pr list --head "$BRANCH" --json number,title,url
Ask user to confirm if ambiguous.
1.2 Fetch PR metadata
# PR details
gh pr view $PR_NUM --json title,body,author,files,baseRefName,headRefName
# Full diff
gh pr diff $PR_NUM
# Existing review comments
gh api repos/{owner}/{repo}/pulls/$PR_NUM/comments \
--jq '.[] | {path: .path, line: .line, body: .body, id: .id, user: .user.login, in_reply_to_id: .in_reply_to_id}'
# Review submissions (approvals, change requests)
gh api repos/{owner}/{repo}/pulls/$PR_NUM/reviews \
--jq '.[] | {id: .id, user: .user.login, state: .state, body: .body}'
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.
- yesterday Changed · +7 lines d9be86ef4616
- 1mo ago Changed · +156 lines fcfb6083a4fe
- 2mo ago First seen · 654 lines · 43 tokens per session scan A 246a98f8c514
pr-review is a skill published in the GitHub repository jamestexas/agents (2 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 8,189 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
code-commit
Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.
spec-finish
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete"…
pr-review
Intent-aware map-reduce PR review with CI/CD support, confidence gating, and intelligent comment deduplication.
pr-walkthrough
Generate an evidence-grounded markdown walkthrough for a pull request.