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 tonyghiani/ai-essentials --skill review-prgit clone --depth 1 https://github.com/tonyghiani/ai-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/tonyghiani/ai-essentials/review-pr)<a href="https://agentmods.dev/skills/tonyghiani/ai-essentials/review-pr"><img src="https://agentmods.dev/badge/skills/tonyghiani/ai-essentials/review-pr/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/tonyghiani/ai-essentials/review-pr"><img src="https://agentmods.dev/badge/skills/tonyghiani/ai-essentials/review-pr.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.00074 | $0.01163 |
| Opus 5 | $0.00037 | $0.00581 |
| Sonnet 5 | $0.00015 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
review-pr 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
Fetch a GitHub PR, check out its branch, run the review-team skill, and transform the report into copy-pasteable conventional comments.
Path resolution
Paths below are relative to this skill's directory (~/.claude/skills/review-pr/
for a Claude Code install).
Inputs
The user provides a GitHub PR URL (e.g. https://github.com/org/repo/pull/123).
Extract OWNER/REPO and PR_NUMBER from the URL.
Workflow
Step 1 — Fetch PR and check out the branch
Before checkout, verify git state:
git status --porcelain
If the working tree is dirty, warn the user and ask whether to proceed, stash,
or use git worktree add for an isolated checkout.
gh pr view $PR_NUMBER --repo $OWNER/$REPO --json title,body,baseRefName,headRefName,files,additions,deletions,author
gh pr checkout $PR_NUMBER --repo $OWNER/$REPO --detach
Record the previous branch/ref (git rev-parse --abbrev-ref HEAD before
checkout if needed) so you can tell the user how to return.
If the PR has more than 50 changed files, warn the user and ask whether to proceed or narrow the scope.
Step 2 — Run the review-team skill
Read and follow ../review-team/SKILL.md using branch review mode.
The checked-out PR branch is the HEAD; the base branch from PR_META is the
comparison target.
The review-team skill handles gathering context, reading reviewer personas, launching 6 parallel reviewers, and consolidating findings into a report.
Step 3 — Transform report into conventional comments
Take the Review Team Report from Step 2 and convert each finding into a comment ready to copy-paste onto the GitHub PR.
Severity → conventional comment label mapping
| Report severity | Conventional label |
|---|---|
| Critical | issue (blocking): |
| Important | suggestion: |
| Minor | nitpick (non-blocking): |
| Praise (from Reviewer-Specific Notes or inline) | praise: |
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.
- 9d ago First seen · 146 lines · 74 tokens per session scan A 628bba08de63
review-pr is a skill published in the GitHub repository tonyghiani/ai-essentials (6 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 1,163 once invoked, about $0.0004 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-31.
Other skills, from other repositories
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.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.