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 ayushcodes10/echo-mem --skill source-command-swarm-developmentgit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/ayushcodes10/echo-mem/source-command-swarm-development)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/source-command-swarm-development"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-swarm-development/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/ayushcodes10/echo-mem/source-command-swarm-development"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-swarm-development.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.00015 | $0.00584 |
| Opus 5.5 | $0.00006 | $0.00234 |
| Sonnet 5.5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
source-command-swarm-development 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 1mo 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.
source-command-swarm-development
Use this skill when the user asks to run the migrated source command swarm-development.
Command Template
Development Swarm Strategy
Purpose
Coordinated development through specialized agent teams.
Activation
Using MCP Tools
// Initialize development swarm
mcp__claude-flow__swarm_init({
"topology": "hierarchical",
"maxAgents": 8,
"strategy": "balanced"
})
// Orchestrate development task
mcp__claude-flow__task_orchestrate({
"task": "build feature X",
"strategy": "parallel",
"priority": "high"
})
Using CLI (Fallback)
npx Codex-flow swarm "build feature X" --strategy development
Agent Roles
Agent Spawning with MCP
// Spawn development agents
mcp__claude-flow__agent_spawn({
"type": "architect",
"name": "System Designer",
"capabilities": ["system-design", "api-design"]
})
mcp__claude-flow__agent_spawn({
"type": "coder",
"name": "Frontend Developer",
"capabilities": ["react", "typescript", "ui"]
})
mcp__claude-flow__agent_spawn({
"type": "coder",
"name": "Backend Developer",
"capabilities": ["nodejs", "api", "database"]
})
mcp__claude-flow__agent_spawn({
"type": "specialist",
"name": "Database Expert",
"capabilities": ["sql", "nosql", "optimization"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Integration Tester",
"capabilities": ["integration", "e2e", "api-testing"]
})
Best Practices
- Use hierarchical mode for large projects
- Enable parallel execution
- Implement continuous testing
- Monitor swarm health regularly
Status Monitoring
// Check swarm status
mcp__claude-flow__swarm_status({
"swarmId": "development-swarm"
})
// Monitor agent performance
mcp__claude-flow__agent_metrics({
"agentId": "architect-001"
})
// Real-time monitoring
mcp__claude-flow__swarm_monitor({
"swarmId": "development-swarm",
"interval": 5000
})
Error Handling
// Enable fault tolerance
mcp__claude-flow__daa_fault_tolerance({
"agentId": "all",
"strategy": "auto-recovery"
})
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.
- 1mo ago First seen · 108 lines · 15 tokens per session scan A 19b9bb11c5ab
source-command-swarm-development is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 584 once invoked, about $0.0001 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-12.
Other skills, from other repositories
verify
Build, launch, and drive a local Honcho stack to verify a change at its runtime surface (the /v3 HTTP API and the deriver queue). Use when verifying a diff or confirming a change works in the running app.
remindb-setup
Config-first setup wizard for a remindb MCP server — run it as /remindb-setup (interactive), /remindb-setup automode (hands-off), or /remindb-setup only-config (bridge hosts: author .remindb/ only, no env wiring). Two passes. First-time (no server attached yet): detect the host, author the .remindb/ config…
squish
ALWAYS use this skill when working with agents, memory, context, persistence, or AI agent state. Use when the user mentions: 'the agent forgot', 'save this', 'remember that', 'context is lost', 'memory', 'MCP server', 'agent memory', 'persistent memory', 'session context', 'project context', 'recall', 'remember'…
squish-memory
Persistent memory system for Claude Code. Use when you need to store, recall, or search project memories, facts, decisions, and learnings across sessions. Triggers on: remember, recall, memory, forget, search memories, store context, project knowledge, what did we decide, previous conversation.
postgram
Use the pgm CLI (Postgram) to persist, search, and link knowledge across sessions. Invoke whenever the user wants to remember something across conversations, recall prior context, search their personal knowledge base, track tasks, or explore relationships between stored entities. Assumes pgm is on PATH, PGMAPIURL is…
aura
Give this agent a real email address, a webhook URL, durable memory across runs, and the ability to wait for an event without burning tokens. Use when a task needs a verification code sent by email, needs to wait for a webhook or an approval, needs to remember something after the session ends, or needs to survive a…