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 skills/sonichi/sutando/pr-shepherd-contractnpx skills add sonichi/sutando --skill pr-shepherd-contractgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/pr-shepherd-contract)<a href="https://agentmods.dev/skills/sonichi/sutando/pr-shepherd-contract"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/pr-shepherd-contract.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.00053 | $0.00446 |
| Opus 5 | $0.00026 | $0.00223 |
| Sonnet 5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
pr-shepherd-contract 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 6d 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 Shepherd Contract (GitHub adapter)
The GitHub binding for the provider-neutral shepherd contract
(src/shepherd_contract.py). The contract defines WHAT a shepherd task is
responsible for and WHICH observed events count; this skill supplies the
GitHub-specific half:
- Observation —
observe(repo, number)reads live PR state via the GitHub CLI (gh api) and emits oneObservedEvent(merged / closed unmerged / updated). - Actor resolution —
resolve_actor(repo, number)uses the last non-merge commit's author email (git.commit_author_email), not the account login, because several actors can push under one login. - Persistence —
save(task_id, scope, state)/load(task_id)/resume(task_id)keep the durable contract record under<workspace>/state/shepherd/, create-or-advance only (never rebind), so a different process can pick the objective up later.
Usage
Import from the skill's scripts directory (the module bootstraps src/ onto
sys.path itself):
import sys, pathlib
sys.path.insert(0, str(repo_root / "skills" / "pr-shepherd-contract" / "scripts"))
import shepherd_github as g
scope = g.scope_for("owner/repo", 123, g.resolve_actor("owner/repo", 123))
g.save("task-abc", scope, "waiting", "shepherding PR 123")
# ... later, any process:
state, why = g.resume("task-abc")
Tests: tests/shepherd-github-durability.test.py,
tests/shepherd-github-integrity.test.py (contract policy itself:
tests/shepherd-contract-admission.test.py).
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.
- 6d ago First seen · 43 lines · 53 tokens per session scan A cb506c9d4b61
pr-shepherd-contract is a skill published in the GitHub repository sonichi/sutando (391 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 446 once invoked, about $0.0003 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
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.