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 AndrewNgGirl/SkillLens --skill pr-reviewergit clone --depth 1 https://github.com/AndrewNgGirl/SkillLensWrote 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/andrewnggirl/skilllens/pr-reviewer)<a href="https://agentmods.dev/skills/andrewnggirl/skilllens/pr-reviewer"><img src="https://agentmods.dev/badge/skills/andrewnggirl/skilllens/pr-reviewer/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/andrewnggirl/skilllens/pr-reviewer"><img src="https://agentmods.dev/badge/skills/andrewnggirl/skilllens/pr-reviewer.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.00065 | $0.01509 |
| Opus 5 | $0.00032 | $0.00754 |
| Sonnet 5 | $0.00013 | $0.00302 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
pr-reviewer 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 7d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-reviewer
When to use
When the user asks to review / audit / comment / 评审 / 审查 a GitHub PR by URL or local diff. Trigger phrases include:
- "帮我 review 这个 PR"
- "review https://github.com/.../pull/123"
- "check this diff before I merge"
Not suitable for: bug-hunting (use Copilot Code Review), security scans (use CodeQL), runtime performance review.
Target users
- Open-source maintainers handling 5–20 PRs/week
- Small dev teams (3–8 engineers) without a dedicated reviewer
- Solo developers who want a second pair of eyes on style and structure
Estimated frequency: per-PR (high-frequency, daily for active repos).
Why this skill
Unlike GitHub Copilot Code Review (focuses on bugs) or CodeQL (focuses on security), pr-reviewer focuses on team-specific style and structural conventions — the kind of rules that are written down in your team handbook but no off-the-shelf tool knows about.
Quantified value: cuts the average human "first-pass review" from ~30 min to ~5 min per PR — saves about 25 min/PR × 10 PRs/week ≈ 4 h/week per reviewer.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
pr_url |
string | yes | e.g. https://github.com/owner/repo/pull/123 |
team_rules |
string | optional | path to team convention markdown; defaults to references/default-rules.md |
language |
enum | optional | one of python, typescript, go; auto-detect if omitted |
Cache key: SHA-256 of (pr_url, head_sha, team_rules_hash) — same PR + same head SHA reuses cached review without re-calling the LLM.
Workflow
- Fetch diff: call
scripts/fetch_pr.pywithpr_url→ returns unified diff + file list. - Static lint: run language-specific linter (
ruff/eslint/golangci-lint) for objective issues. - Style review (LLM): feed diff +
team_rulesto the LLM, ask for ≤ 5 most impactful style issues with line refs. - Compose comments: merge linter issues + LLM issues into JSON, deduplicated by
(file, line, message_first_30_chars). - Validate output: pass through
scripts/validate_review.pyagainstassets/review.schema.json; on fail, regenerate once, then escalate to user. - Output: structured JSON ready for
gh pr review --commentor copy-paste into a GitHub review.
What ships with it
9 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.
- 7d ago First seen · 128 lines · 65 tokens per session scan A a8a0ece73f02
pr-reviewer is a skill published in the GitHub repository AndrewNgGirl/SkillLens (75 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 1,509 once invoked, about $0.0003 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-03.
Other skills, from other repositories
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
chained-pr
Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.