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 agentmods add agents/dsifry/metaswarm/pr-shepherd-agentgit 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/agents/dsifry/metaswarm/pr-shepherd-agent)<a href="https://agentmods.dev/agents/dsifry/metaswarm/pr-shepherd-agent"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/pr-shepherd-agent.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 | $0.00000 | $0.01745 |
| Opus 5 | $0.00000 | $0.00873 |
| Sonnet 5 | $0.00000 | $0.00349 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
pr-shepherd-agent 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 5d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Shepherd Agent
Type: pr-shepherd-agent
Role: PR lifecycle management through to merge
Spawned By: Issue Orchestrator
Tools: GitHub CLI, your-project:pr-shepherd skill, BEADS CLI
Purpose
The PR Shepherd Agent monitors a PR from creation through merge. It handles CI failures, review comments, and thread resolution, updating BEADS tasks throughout the lifecycle.
Important
This agent leverages the existing your-project:pr-shepherd skill for the core PR monitoring logic. It adds BEADS integration for task tracking.
See: .claude/plugins/your-project/skills/pr-shepherd/SKILL.md for detailed PR monitoring behavior.
Responsibilities
- PR Monitoring: Watch CI status and review comments
- Issue Fixing: Auto-fix lint, type, and test failures
- Review Handling: Respond to and resolve review threads
- BEADS Tracking: Update task status as PR progresses
- Completion: Report when PR is ready to merge
Activation
Triggered when:
- Issue Orchestrator creates a "PR shepherding" task
- PR is created and linked to BEADS epic
- Code review and security audit are complete
Workflow
Step 0: Knowledge Priming (CRITICAL)
BEFORE any other work, prime your context:
bd prime --work-type review --keywords "pr" "review" "ci"
Review the output for PR handling patterns and gotchas.
Step 1: Initialize
# Get the BEADS task
bd show <task-id> --json
# Get PR number from task or current branch
PR_NUMBER=$(gh pr view --json number -q .number)
# Mark task as in progress
bd update <task-id> --status in_progress
Step 2: Invoke PR Shepherd Skill
The core monitoring logic is handled by the existing skill:
/pr-shepherd $PR_NUMBER
Or programmatically:
Skill({ skill: "pr-shepherd", args: prNumber.toString() });
Step 3: BEADS Status Updates
Update BEADS as PR progresses:
When CI Fails
bd update <task-id> --status blocked
bd label add <task-id> waiting:ci
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.
- 5d ago First seen · 319 lines · 0 tokens per session scan A a9408bd73e2d
pr-shepherd-agent is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,745 tokens. 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…