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 agents/soulcynics404/agentforge/agent-spawninggit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/agents/soulcynics404/agentforge/agent-spawning)<a href="https://agentmods.dev/agents/soulcynics404/agentforge/agent-spawning"><img src="https://agentmods.dev/badge/agents/soulcynics404/agentforge/agent-spawning.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.00000 | $0.00175 |
| Opus 5 | $0.00000 | $0.00088 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
agent-spawning 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 yesterday.
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.
This is a copy
100% identical to agent-spawning — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Using Claude Code's Task Tool
CRITICAL: Always use Claude Code's Task tool for actual agent execution:
// Spawn ALL agents in ONE message
Task("Researcher", "Analyze requirements...", "researcher")
Task("Coder", "Implement features...", "coder")
Task("Tester", "Create tests...", "tester")
MCP Coordination Setup (Optional)
MCP tools are ONLY for coordination:
mcp__claude-flow__swarm_init { topology: "mesh" }
mcp__claude-flow__agent_spawn { type: "researcher" }
Best Practices
- Always spawn agents concurrently
- Use Task tool for execution
- MCP only for coordination
- Batch all operations
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.
- yesterday First seen · 29 lines · 0 tokens per session scan A 74bfe922137a
agent-spawning is an agent published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 175 tokens. A static security scan graded it A with 0 findings. It is 100% identical to agent-spawning, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
STYLE
There are exactly two shapes in this pack. Pick one and stay in it.
TAGS
Auto-generated tags (json, JSON, Json, json-parsing) fragment the routing index. A curated list makes the orchestrator's job tractable: when it looks up bytag.security, it gets every agent that should be there, not half of them plus a scatter of secure, sec, security-audit.
agents
Agent 模块是系统的执行引擎，基于 LangGraph StateGraph 实现单个 Agent 的完整执行生命周期管理。.
coder
Software engineer — implements features, writes tests, fixes bugs.
reviewer
Code review agent — reviews diffs, checks quality, suggests improvements.
sec-auditor
Security audit agent — scans for vulnerabilities, checks permissions, reviews secrets.