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 desplega-ai/agent-swarm --skill review-prgit clone --depth 1 https://github.com/desplega-ai/agent-swarmWrote 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/desplega-ai/agent-swarm/review-pr)<a href="https://agentmods.dev/skills/desplega-ai/agent-swarm/review-pr"><img src="https://agentmods.dev/badge/skills/desplega-ai/agent-swarm/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/desplega-ai/agent-swarm/review-pr"><img src="https://agentmods.dev/badge/skills/desplega-ai/agent-swarm/review-pr.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.00022 | $0.00967 |
| Opus 5 | $0.00011 | $0.00483 |
| Sonnet 5 | $0.00004 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00097 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Pull Request / Merge Request
Review a PR (GitHub) or MR (GitLab) by analyzing changes and providing structured feedback.
Provider detection: Check the remote URL or provided URL:
- If GitHub → use
gh prcommands - If GitLab → use
glab mrcommands
Arguments
pr-number-or-url: Either a PR number (e.g.,123) or a full URL
Workflow
1. Setup
- Ensure the repo is cloned to
/workspace/personal/<repo-name>(clone withgh repo cloneif needed) - Fetch, checkout the PR branch, get PR details and diff
2. Check CI Status (MANDATORY)
Check CI with gh pr checks <pr-number> (or glab mr view --json pipelines).
If CI checks are failing, this is an automatic REQUEST_CHANGES. Do not approve a PR with failing CI. Include the failing check names and error details in your review.
2b. Review Repository Guidelines
Check the "Review Guidance" section of your Repository Guidelines for repo-specific review instructions (e.g., "check README.md", "enforce camelCase in specific directories"). Apply these instructions during your review below.
Also note the repo's Merge Policy — check allowMerge and mergeChecks before approving or merging. If allowMerge is false, do NOT merge — only review and approve/request changes.
3. Verify Tests Are Included (MANDATORY)
Check that the PR includes test changes. If the PR modifies code but does not add or update tests, this is an automatic REQUEST_CHANGES. Every code change must include corresponding tests.
Exceptions:
- Pure documentation changes (README, comments only)
- Configuration-only changes (CI config, linter config, env files)
- Dependency version bumps with no code changes
When requesting changes for missing tests, be specific about what tests are needed.
4. Analyze the Changes
Review the diff for:
- Security issues: SQL injection, XSS, command injection, secrets in code
- Logic errors: Off-by-one errors, null handling, edge cases
- Performance concerns: N+1 queries, unnecessary loops, memory leaks
- Code quality: Naming, complexity, duplication, missing error handling
- Test coverage: Are included tests sufficient? Do they cover edge cases?
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 · 113 lines · 22 tokens per session scan A 6389eddf8767
review-pr is a skill published in the GitHub repository desplega-ai/agent-swarm (761 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 967 once invoked, about $0.0001 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
agent-swarm-pr
Agent skill for swarm-pr - invoke with $agent-swarm-pr.
agent-pr-manager
Agent skill for pr-manager - invoke with $agent-pr-manager.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.