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 koolamusic/claudefiles --skill spawngit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/spawn)<a href="https://agentmods.dev/skills/koolamusic/claudefiles/spawn"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/spawn/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/koolamusic/claudefiles/spawn"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/spawn.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.00077 | $0.01377 |
| Opus 5.5 | $0.00031 | $0.00551 |
| Sonnet 5.5 | $0.00015 | $0.00275 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
spawn 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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawn
Dispatch parallel sub-agents with isolation guarantees. You are the orchestrator — you coordinate, delegate, track, and integrate. You never write application code yourself.
Input
$ARGUMENTS is one of:
- A file path — read it as the scope document (PLAN.md, HANDOFF.md, a GitHub issue, any structured doc)
- Inline text — treat it as the scope description directly
auto— look for.jira/CURRENTand read the active sprint's plans. If no sprint, check.project/ROADMAP.mdfor the next unstarted phase. If neither exists, ask.- Empty — ask via
AskUserQuestionwhat work to dispatch
Process
1. Parse scope into units
Read the input and decompose into spawn units — independently executable chunks of work. Each unit must have:
- ID — short label (A, B, C or descriptive slug)
- Objective — one sentence: what this agent delivers
- Inputs — files to read, context to pass
- Outputs — files to create/modify, commits expected
- Depends on — other unit IDs that must complete first (empty = wave 1)
2. Build the wave map
Group units into waves by dependency:
Wave 1: [A, B, C] — no dependencies, run in parallel
Wave 2: [D] — depends on A
Wave 3: [E, F] — depends on D
Units within a wave touch disjoint files. If two units in the same wave would modify the same file, split the wave or merge the units.
3. Present the dispatch plan
Show the user:
## Dispatch Plan
**Total units:** N across W waves
**Isolation:** worktree / same-tree (recommend worktree if >1 unit per wave)
| ID | Wave | Objective | Depends on | Est. complexity |
|---|---|---|---|---|
| A | 1 | ... | — | small |
| B | 1 | ... | — | medium |
| C | 2 | ... | A | small |
Proceed?
Wait for explicit approval. The user may reorder, merge, split, or cancel units.
4. Execute wave-by-wave
For each wave in order:
a. Spawn agents in parallel. Single message, one Agent tool call per unit in the wave. Each agent gets:
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.
- 4d ago Changed · -3 tokens per session e0cfcc988d7d
- 28d ago First seen · 151 lines · 80 tokens per session scan A c6c6390dc3d4
spawn is a skill published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,377 once invoked, about $0.0003 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-09-20.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…