Borrowing it
Nothing to install: this file belongs to ra3orblade/swarm. 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/ra3orblade/swarm/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/ra3orblade/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/ra3orblade/swarm/pr)<a href="https://agentmods.dev/skills/ra3orblade/swarm/pr"><img src="https://agentmods.dev/badge/skills/ra3orblade/swarm/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/ra3orblade/swarm/pr"><img src="https://agentmods.dev/badge/skills/ra3orblade/swarm/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.00045 | $0.00361 |
| Opus 5.5 | $0.00018 | $0.00144 |
| Sonnet 5.5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
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 2mo 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
PR
Get finished, verified work onto a branch and into a PR. This is the last mile — if the work is a plan task, run /chores first (it calls this).
Steps
- Confirm green (quick if
/choresjust ran):bun run typecheck && bun run test. - Branch — if on
main/detached, createfeat/<short-slug>first. Feature work never commits tomaindirectly. - Commit scoped —
git add <explicit paths>(never-Ain a shared checkout), one focused commit. Message: what changed + how verified; end with:Co-Authored-By: Claude <[email protected]> - Push —
git push -u origin <branch>(add--force-with-leaseonly after a rebase). - Open the PR from the real diff:
Body: a sentence on what it does, the key implementation notes, and the verification line (gh pr create --title "<concise>" --body "<what/why + verification + test count>"typecheck · lint · test (N pass) · smoke · docs). Keep one PR to a coherent batch of related tasks. - Print the PR URL.
Do not merge. Rate discipline: few, substantial PRs; push rarely and deliberately.
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.
- 2mo ago First seen · 26 lines · 45 tokens per session scan A 6aa82b43ccbf
pr is a skill published in the GitHub repository ra3orblade/swarm (14 stars, last pushed 3d ago), licensed Apache-2.0. It adds 45 tokens to every session and 361 once invoked, about $0.0002 per session on Opus 5.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
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
prepare-pr
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.
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.