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 eshwarvijay/secondmate --skill secondmate-dispatchgit clone --depth 1 https://github.com/eshwarvijay/secondmateWrote 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/eshwarvijay/secondmate/secondmate-dispatch)<a href="https://agentmods.dev/skills/eshwarvijay/secondmate/secondmate-dispatch"><img src="https://agentmods.dev/badge/skills/eshwarvijay/secondmate/secondmate-dispatch/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/eshwarvijay/secondmate/secondmate-dispatch"><img src="https://agentmods.dev/badge/skills/eshwarvijay/secondmate/secondmate-dispatch.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.00185 | $0.24156 |
| Opus 5.5 | $0.00074 | $0.09662 |
| Sonnet 5.5 | $0.00037 | $0.04831 |
| Haiku 4.5 | $0.00018 | $0.02416 |
Grade A, and why
secondmate-dispatch scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
called with an argv array (e.g. `subprocess.run([...])`, bash `"${arr[@]}"`), never a string How it starts
The opening of the file, as written. The whole thing — 1,268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
secondmate-dispatch — external OS-process dispatcher
Scope
This file is for a dispatcher process that is itself not a Claude Code session: a cron job, a
long-running shell daemon, Hermes, or any other agent/scheduler with terminal access. It spawns
each sub-agent-supervisor as a separate OS process (claude -p ...) rather than an Agent-tool
call, and it has no ScheduleWakeup, no in-session hold UI, and no Agent-tool return value — only
files on disk and process exit codes. skills/secondmate/SKILL.md is the single source of truth
for everything about what the sub-supervisor does once it is running (Plan Committee, Triage,
Spawn, Guard, Check, Gate, Hold, Integrate, Teardown, Audit trail, Lesson feedback) — that file's
in-session Agent-tool top level is unedited and unaffected by this one. This file covers only what
changes for how the dispatcher itself launches, watches, and closes out that same contract when
it is an external OS process instead of an Agent-tool call.
The same contract, restated briefly
Read skills/secondmate/SKILL.md's "Dispatch mechanics — solo and batch" section before using this
file — it is not reproduced here beyond this pointer summary:
- Trigger test — dispatch (never run the loop inline) once a task is iterative (multiple edit→check rounds) and verifiable (tests/build/lint/a live call proves it) and risky/outward-facing (commit, push, PR, deploy, delete, external write). All three must hold.
- Batch cap — at most 10 concurrent sub-supervisors per batch, a hard, non-tunable constant
(
N=10). More than 10 independent tasks: run 10 now, queue the rest for the next batch. - Solo vs. batch — one task → solo dispatch, one fresh sub-supervisor, its own hold, its own merge. Several genuinely independent tasks handed over together → batch dispatch, up to 10 fresh sub-supervisors, one consolidated human hold for the whole batch, not one per task-id.
- Solo sub-supervisor steps 1–7 and batch sub-supervisor steps (a)–(d) are unchanged —
claim → derive names → run the existing solo SOP, recording
progress-ledger.pycheckpoints → (batch only) stop atSM_READY_UNMERGEDinstead of self-merging → release claim (solo) or leave it open (batch, until the consolidated hold is answered) → emit exactly one completion tag. See that section for the exactclaim-ledger.py/progress-ledger.pyinvocations at each step. - One explicit exception to "unchanged": Spawn. When this external dispatcher does the
spawning, it has already created the worktree and
cd'd into it beforeclaude -peven starts (section 1) — the sub-supervisor's own copy of the parent SOP's Spawn step must not create a second one. See section 1's "Spawn is the one overridden step" below for the exact override to put in the sub-supervisor's prompt.
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 · 1,268 lines · 185 tokens per session scan A 41df04dca0b6
secondmate-dispatch is a skill published in the GitHub repository eshwarvijay/secondmate (5 stars, last pushed yesterday), licensed MIT. It adds 185 tokens to every session and 24,156 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.
Other skills, from other repositories
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
triage
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
code-review
The depth half of a review - the dimensions a diff is read against (correctness, boundaries, concurrency, failure paths, secrets, data access, structure, test quality) and the rule that a finding is refuted before it is reported. The verdict stays with the reviewer agent. Use when reviewing a diff or a pull request…
deslop
The optimization pass, defined - delete before you add, one smell class per pass, behaviour pinned by a test that ran BEFORE the edit. Lints a SKILL.md and prose by the same instinct. Use for the per-story optimization pass or when code has grown noisy without growing capable.
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.