Borrowing it
Nothing to install: this file belongs to huacnlee/omamail. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huacnlee/omamail/main/.agents/skills/review-prs/SKILL.mdgit clone --depth 1 https://github.com/huacnlee/omamailWrote 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/huacnlee/omamail/review-prs)<a href="https://agentmods.dev/skills/huacnlee/omamail/review-prs"><img src="https://agentmods.dev/badge/skills/huacnlee/omamail/review-prs/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/huacnlee/omamail/review-prs"><img src="https://agentmods.dev/badge/skills/huacnlee/omamail/review-prs.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.03949 |
| Opus 5 | $0.00022 | $0.01975 |
| Sonnet 5 | $0.00009 | $0.00790 |
| Haiku 4.5 | $0.00004 | $0.00395 |
Grade A, and why
review-prs 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 2d 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.
Honor repository-specific security gates. In Omamail this includes curl-config validation before any process starts (the entire batch), curl `-q` first and `--globoff`, credentials over stdin, configured-origin restricti How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PRs
Accept optional PR numbers, URLs, or a repository/queue filter. Examples: $review-prs 42 57, $review-prs https://github.com/owner/repo/pull/42, or $review-prs review all open non-draft PRs in this repository.
Scope and authority
- Resolve the repository from explicit arguments or the current checkout. If that is ambiguous, ask only for the repository. With explicit PR numbers or URLs, review only those PRs, deduplicated and in supplied order; never add other candidates. Without PR targets, inspect open PRs and their review/discussion history, order by creation time oldest to newest, and select at most the oldest three open non-draft PRs needing review or re-review. A PR needing re-review has a new head or an explicit re-review request since the prior completed review; skip unchanged PRs already reviewed by this reviewer and explain the skip. Paginate listings/history before selection so an API page does not silently omit older PRs.
- Keep each review batch to at most three PRs, and still process them one at a time. If explicit targets exceed three, split only those targets into successive batches of at most three and finish one batch before starting the next. Without explicit targets, stop after the selected batch of at most three and report remaining candidates; do not drain the queue automatically. Read each selected PR's previous findings, author responses and revisions to distinguish first review from re-review.
- Explicitly invoking this workflow authorizes dedicated worktrees, investigation and validation, PR title/body edits, and publishing passing reviews on the selected PRs. For PRs with actionable findings, first complete the review and ask the user to choose helping fix them or submitting Request Changes, as defined below. Fixes, fix commits/pushes and Request Changes publication require that decision; explicit session authorization for a specific choice satisfies it. A request for a read-only review or draft overrides these defaults. Automatic skill selection alone grants no authority to publish, push, or edit GitHub; use existing session authorization or prepare the complete result before asking for missing approval.
- Do not merge, enable auto-merge, force-push, change branch protection, or dismiss other reviewers' decisions without separate explicit authorization. Do not ask again for actions already authorized.
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.
- 2d ago First seen · 98 lines · 43 tokens per session scan A be1c4e93fdce
review-prs is a skill published in the GitHub repository huacnlee/omamail (206 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 3,949 once invoked, about $0.0002 per session on Opus 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-08.
Other skills, from other repositories
mail-operations
Use this skill whenever the user wants to interact with email. This includes reading inbox, sending emails, replying, searching messages, managing labels and categories, downloading attachments, setting up auto-reply rules, or triggering agents to handle incoming emails. Supports Gmail, Outlook, and IMAP/SMTP (QQ…
c-email
Read, send, search, and label email via gog (Gmail CLI) or himalaya (IMAP). Supports inbox management, drafting replies, thread viewing, and label/folder operations across Gmail and standard IMAP accounts.
imap-smtp-email
Read, search, and manage email via IMAP protocol. Send email via SMTP. Supports Gmail, Outlook, 163.com, 126.com, QQ Mail, and any standard IMAP/SMTP server with multi-account support.
mailbox
A command-line email tool for reading, searching, sending, and managing messages in Gmail, QQ, 163, Outlook, and other IMAP/SMTP accounts.
Run the external email CLI through exec for real IMAP/SMTP/Notmuch mailboxes. Use when the user explicitly wants a real terminal email workflow instead of the built-in benchmark email surfaces.
email-manager
Read, search, send, and manage email via IMAP/SMTP or API (Gmail, Outlook).