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 skyfox675/agents-skills --skill dispatching-subagentsgit clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/skyfox675/agents-skills/dispatching-subagents)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/dispatching-subagents"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/dispatching-subagents.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.00211 | $0.05788 |
| Opus 5 | $0.00105 | $0.02894 |
| Sonnet 5 | $0.00042 | $0.01158 |
| Haiku 4.5 | $0.00021 | $0.00579 |
Grade A, and why
dispatching-subagents 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.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Sub-Agents
This skill is the dispatch half of a multi-agent issue-orchestration system. It covers everything between "an issue is ready to work" and "a sub-agent has opened a PR": picking the issue, resolving model and effort, writing the brief, launching in parallel, recovering stalls, and verifying completions.
Companions in the same family: the issue-filing skill (gh-issue-filing for GitHub, jira-issue-filing for Jira) defines what a dispatchable issue looks like; the issue control-field skill (gh-issue-labels for GitHub labels, jira-issue-fields for Jira fields) defines the control taxonomy this skill reads; the issue-locking skill (gh-issue-locking / jira-issue-locking) defines the claim that must precede every dispatch; the orchestrating-slots skill runs the loop that calls this one; the driving-prs-to-merge skill defines what the agent owes after gh pr create.
Project bindings
Every value below is project-specific. The adopting project must define these in its own CLAUDE.md; this skill refers to them by placeholder. Do not copy the example column into a new project unverified.
| Binding | Placeholder | Example |
|---|---|---|
| Integration branch PRs target | <integration-branch> |
dev (NOT the default branch, so issue auto-close never fires — close explicitly on merge) |
| Repo root | <repo-root> |
resolve dynamically: git rev-parse --show-toplevel — hardcoding a path rots |
| Worktree location | <worktree-dir> |
<repo-root>/.worktrees/<name> (git-ignored) |
| Branch naming | <branch-convention> |
feat|fix|chore|docs/<N>-<slug> (encodes the issue number) |
| Commit message convention | <commit-convention> |
lowercase conventional-commit subject (lowercase because the project's title-format check may reject leading capitals); body ends with Closes #<N> |
| Toolchain prefix for git hooks | <toolchain-prefix> |
e.g. a runtime-version bootstrap such as source <version-manager> && use <version> && (empty if the project's hooks need no runtime bootstrap, or it has no hooks) |
| Lockfile-faithful install | <lockfile-install-cmd> |
the ecosystem's frozen-lockfile install (e.g. <pkg-manager> install --frozen-lockfile) |
| Force-push policy | <force-push-policy> |
sub-agents may force-push their own branch with --force-with-lease; orchestrator handles any case where permission-blocking applies |
| Derived files never committed | <derived-files> |
generated status/manifest files (regenerated by post-merge automation) |
| Model tiers | <cheap-model> / <workhorse-model> / <premium-models> |
haiku / sonnet / opus, fable |
| Auto-merge invocation | <auto-merge-cmd> |
gh pr merge <N> --auto — verify whether a strategy flag is accepted; some merge queues reject one and enrollment silently drops |
| Pre-push hook cost | <hook-cost> |
e.g. several minutes (full local unit suite) |
| Traceability scheme (optional) | <traceability-scheme> |
REQ-<PREFIX>-<NUMBER> tags in test names |
| Design source of truth (UI projects) | <design-source> |
the project's authoritative design artifacts (e.g. a checked-in design-system/ folder or a referenced design tool) |
| Test-layer menu | <test-layers> |
unit / integration / smoke / E2E |
| Bot reviewer(s) | <bot-reviewer> |
the project's automated PR-review bot, if any |
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 · 288 lines · 211 tokens per session scan A 1007092d8363
dispatching-subagents is a skill published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 6d ago), licensed MIT. It adds 211 tokens to every session and 5,788 once invoked, about $0.0011 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.