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 caipe-io/ai-platform-engineering --skill review-open-pull-requestsgit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWrote 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/caipe-io/ai-platform-engineering/review-open-pull-requests)<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/review-open-pull-requests"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/review-open-pull-requests/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/caipe-io/ai-platform-engineering/review-open-pull-requests"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/review-open-pull-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00386 |
| Opus 5 | $0.00026 | $0.00193 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
review-open-pull-requests 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 11d 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.
What it actually says
Review Open Pull Requests
Retrieve all open pull requests across configured repositories and present an organized view of their status, reviewers, CI results, and staleness.
Instructions
- Fetch open PRs using the GitHub agent. For each PR, collect:
- PR number, title, and author
- Repository name
- Branch name (head -> base)
- Review status (approved, changes requested, pending review, no reviewers)
- CI/CD check status (passing, failing, pending)
- Labels and draft status
- Age (time since creation) and last activity
- Categorize PRs by urgency:
- Needs Immediate Attention: Failing CI, changes requested, or stale (>5 days)
- Ready to Merge: Approved with passing checks
- In Progress: Draft PRs or pending reviews
- Blocked: Has `blocked` or `do-not-merge` labels
- Provide summary statistics
Examples
- "List all open pull requests in our repos"
- "Show me PRs that need review"
- "Which PRs have failing CI checks?"
- "Are there any stale PRs older than a week?"
Guidelines
- Sort PRs by urgency, then by age (oldest first)
- Flag PRs with no assigned reviewers prominently
- Check for conventional commit compliance in PR titles when possible
- Highlight draft PRs separately so they don't clutter the action-needed list
- Include direct links to PRs where possible
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.
- 11d ago First seen · 40 lines · 52 tokens per session scan A b657b083ad37
review-open-pull-requests is a skill published in the GitHub repository caipe-io/ai-platform-engineering (408 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 386 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-08-30.
Other skills, from other repositories
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.
pr-watch-as-author
Watches an authored PR for feedback. Trigger on "watch the PR", "watch this PR and fix comments", or "/pr-watch-as-author" only; never infer intent from an open PR.
pr-open-comments
Triages unresolved PR review comments. Trigger on "address PR comments", "triage PR feedback", "handle the comments", or "/pr-open-comments"; never infer triage intent from unresolved comments.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…