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 dsifry/metaswarm --skill pr-shepherdgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/pr-shepherd)<a href="https://agentmods.dev/skills/dsifry/metaswarm/pr-shepherd"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/pr-shepherd.svg" alt="Measured on agentmods" 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.00027 | $0.04779 |
| Opus 5 | $0.00014 | $0.02389 |
| Sonnet 5 | $0.00005 | $0.00956 |
| Haiku 4.5 | $0.00003 | $0.00478 |
Grade A, and why
pr-shepherd 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 7d 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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-shepherd
Use when a PR has been created and needs to be monitored through to merge - handles CI failures, review comments, and thread resolution automatically until all checks pass and all threads are resolved.
IMPORTANT: This skill is designed for the agent working in a worktree, NOT the orchestrator. The agent handles its own PR monitoring so the orchestrator remains free for other work.
Coordination Mode Note
This skill supports both coordination modes:
- Task Mode (default): Runs as a single long-running
Task()withrun_in_background: true. Orchestrator checks viaTaskOutput(block: false). - Team Mode: Runs as a persistent
shepherdteammate in theissue-{number}team. Sends async status updates viaSendMessage(CI failure, review comments, all-green, PR merged). Orchestrator can respond with instructions (e.g., "defer that comment, create an issue instead"). Responds toshutdown_requestfor graceful exit.
All monitoring, fixing, and review handling logic is identical in both modes. See ./guides/agent-coordination.md for mode detection.
When to Activate
Activate this skill when ANY of these conditions are true:
- Agent just created a PR with
gh pr create - User asks to "shepherd", "monitor", or "see through" a PR
- User invokes
/pr-shepherd <pr-number> - User asks to "watch this PR" or "handle this PR until it's merged"
- Orchestrator spawned you with instructions to shepherd a PR
- Automatic:
bin/create-pr-with-shepherd.shwas used (outputs shepherd instructions)
Automatic Activation via Wrapper Script
When bin/create-pr-with-shepherd.sh creates a PR, it outputs shepherd instructions:
==========================================
PR Shepherd Active for PR #123
==========================================
The pr-shepherd skill will:
- Monitor CI/CD status
- Auto-fix lint, type, and test issues
- Handle review comments
- Resolve threads after addressing feedback
- Report when PR is ready to merge
To manually invoke shepherd later:
/pr-shepherd 123
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.
- 7d ago First seen · 588 lines · 27 tokens per session scan A e88b0a1926f9
pr-shepherd is a skill published in the GitHub repository dsifry/metaswarm (413 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 4,779 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
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.