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/kissrosecicd-hub/agents-evolution/spawnnpx skills add kissrosecicd-hub/agents-evolution --skill spawngit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/spawn)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/spawn"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/spawn.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 | $0.00064 | $0.01091 |
| Opus 5 | $0.00032 | $0.00545 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
meta-agent-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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta: Agent Spawn
Решает когда, кого и сколько субагентов запускать параллельно.
Когда спавнить
| Сигнал | Действие |
|---|---|
| «почини всё», «полный аудит», «комплексная проверка» | Спавн 3-4 агентов параллельно |
| «провери код» на конкретном файле | НЕ спавнить — сделать самому |
| «напиши тесты + документацию» | Спавн 2 агентов (test + docs) параллельно |
| Один запрос, одна задача | НЕ спавнить — оверхед |
Правило: Спавн оправдан когда 3+ независимых задач в одном запросе.
Когда НЕ спавнить
- Задача решается одним действием (один файл, один фикс)
- Пользователь ждёт ответ здесь и сейчас (спавн = задержка)
- Контекст уже загружен и я знаю ответ
- Только один агент нужен (лучше сделать самому)
Выбор агентов по типу задачи
| Тип задачи | Агент(ы) | Параллельно? |
|---|---|---|
| Аудит кода | code-reviewer + security-auditor | ✅ Да, независимы |
| Баг + починить | debugger | ❌ Один агент |
| Баг + тесты | debugger + test-architect | ✅ Да |
| Рефакторинг + документация | refactor-architect + docs-writer | ✅ Да |
| Полный релиз | release-manager | ❌ Один мета-агент |
| Новый проект | onboarding-scout | ❌ Один агент |
| Git + зависимости | git-doctor + dependency-manager | ✅ Да |
Лимиты параллелизма
| Уровень | Макс агентов | Когда |
|---|---|---|
| Минимальный | 2 | Простые независимые задачи |
| Стандартный | 3 | Аудит: code + security + tests |
| Максимальный | 4 | Комплекс: code + security + tests + docs |
| Перебор | 5+ | Контекст деградирует, НЕ делать |
Порядок запуска
Фаза 1 (параллельно, read-only):
├─ code-reviewer → анализ кода
├─ security-auditor → аудит безопасности
└─ onboarding-scout → если новый проект
Фаза 2 (параллельно, зависит от Фазы 1):
├─ debugger → чинит найденные баги
└─ test-architect → пишет тесты
Фаза 3 (последовательно, финализация):
├─ docs-writer → документация изменений
└─ git-doctor → коммит
Правило: Read-only всегда первые. Пишущие — после. Финализация — последовательно.
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 First seen · 108 lines · 64 tokens per session scan A 18b71935a30a
meta-agent-spawn is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,091 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…