Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Sassy-Dog/sassydog-skills/plugin install sassy-dogWrote 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/sassy-dog/sassydog-skills/dispatch-ready)<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/dispatch-ready"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/dispatch-ready/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/sassy-dog/sassydog-skills/dispatch-ready"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/dispatch-ready.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.00174 | $0.18732 |
| Opus 5 | $0.00087 | $0.09366 |
| Sonnet 5 | $0.00035 | $0.03746 |
| Haiku 4.5 | $0.00017 | $0.01873 |
Grade B, and why
dispatch-ready scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`root="$(git rev-parse --show-toplevel 2>/dev/null)"; echo "CONFIG_SOURCE: ${root:-<not a git repo>}"; cat "$root/.claude/sassy-dog/dispatch-ready.md" 2>/dev/null || echo "NO_CONFIG"` How it starts
The opening of the file, as written. The whole thing — 1,074 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatch-Ready
One invocation = one tick of a drain loop.
All state lives in GitHub — status, assignees, PRs, branches — never in conversation memory,
because under /loop each tick may run with no recollection of the previous one. The contract with
groom-backlog: dispatch-ready pulls exclusively from Ready and trusts that Ready means dispatchable.
Anything that smells undispatchable gets bounced back, never patched up inline.
Formerly
drain-it. The "drain it" trigger still resolves here.
1. Repo config
!root="$(git rev-parse --show-toplevel 2>/dev/null)"; echo "CONFIG_SOURCE: ${root:-<not a git repo>}"; cat "$root/.claude/sassy-dog/dispatch-ready.md" 2>/dev/null || echo "NO_CONFIG"
Check CONFIG_SOURCE before using any of this. It is the repo root resolved from the
session's working directory at skill-load time — not necessarily the repo you are about to act
on — and cwd resets between Bash calls, so you cannot influence it. If it names a repo other than
the one you are working in, discard the block above, read that repo's own
.claude/sassy-dog/dispatch-ready.md by absolute path, and use that instead. Config is meant to be applied
exactly as written, so the wrong one silently applies another repo's rules: on 2026-08-18 two agents
shipping in sassydog-routines and sassydog-skills were each handed platform's Terraform gates,
and caught it only by noticing the mismatch themselves.
Frontmatter supplies max_in_flight and review_site, plus the optional board, migrations,
codegen, merge_queue, execution_site, and stacked_prs keys. Contract: sassy-dog:setup-config →
references/config-contract.md.
review_site: decides WHERE this loop's review gate runs — agent, each dispatched sub-agent
reviewing its own diff before it opens a PR (§5), or coordinator, this tick reviewing each open
PR before it merges (§2). Absent selects agent, the fail-safe site. It never decides whether
a review runs or which agent runs it. That is review_agent:'s resolution order, owned by
send-it and unchanged by this key — read it from sassy-dog:setup-config →
references/config-contract.md (review_agent) rather than re-deriving it here.
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.
- 3d ago Changed · +97 lines 383fc8b63e0a
- 5d ago Changed · +158 lines · +6 tokens per session 5b370e42b855
- 8d ago Changed · +17 lines 236735e1f975
- 12d ago First seen · 802 lines · 168 tokens per session scan B f0dc2789e9a3
dispatch-ready is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 174 tokens to every session and 18,732 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.