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.
git clone --depth 1 https://github.com/dshakes/compassWrote 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/commands/dshakes/compass/pr-shepherd)<a href="https://agentmods.dev/commands/dshakes/compass/pr-shepherd"><img src="https://agentmods.dev/badge/commands/dshakes/compass/pr-shepherd/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/commands/dshakes/compass/pr-shepherd"><img src="https://agentmods.dev/badge/commands/dshakes/compass/pr-shepherd.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.00019 | $0.00177 |
| Opus 5.5 | $0.00008 | $0.00071 |
| Sonnet 5.5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
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 1mo 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
Run the pr-shepherd skill on the open PRs: $ARGUMENTS
Follow the skill's procedure exactly: enumerate (fail closed on
isCrossRepository), diagnose each red check from its log, classify
(real defect / mechanical / environmental), fix mechanical failures on the
PR branch with the gate run locally first, three-strikes cap, and stop at
the merge gate. Merge only if --merge was passed or I granted merge
authority earlier in this session; otherwise report ready-to-merge.
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.
- 1mo ago First seen · 14 lines · 19 tokens per session scan A dc084accc506
pr-shepherd is a command published in the GitHub repository dshakes/compass (20 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 177 once invoked, about $0.0001 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-30.
Other commands, from other repositories
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
code-review
Run the code-reviewer subagent on the current diff against origin/development (review-only, no edits).
review-changes
Alias for /code-review kept for backwards compatibility with the existing /feature-pipeline workflow.
audit
Audit a window of recent commits for real defects, confirm each finding before fixing, verify every surface a fix touches, then report confirmed/dismissed/no-op with evidence. Enforces Law 4 (Verify Before Reporting).
gsd:inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.