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-testinggit 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-testing)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/source-command-swarm-testing"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-swarm-testing/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-testing"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-swarm-testing.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.00819 |
| Opus 5.5 | $0.00006 | $0.00328 |
| Sonnet 5.5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
source-command-swarm-testing 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-swarm-testing
Use this skill when the user asks to run the migrated source command swarm-testing.
Command Template
Testing Swarm Strategy
Purpose
Comprehensive testing through distributed execution.
Activation
Using MCP Tools
// Initialize testing swarm
mcp__claude-flow__swarm_init({
"topology": "star",
"maxAgents": 7,
"strategy": "parallel"
})
// Orchestrate testing task
mcp__claude-flow__task_orchestrate({
"task": "test application",
"strategy": "parallel",
"priority": "high"
})
Using CLI (Fallback)
npx Codex-flow swarm "test application" --strategy testing
Agent Roles
Agent Spawning with MCP
// Spawn testing agents
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Unit Tester",
"capabilities": ["unit-testing", "mocking", "coverage"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Integration Tester",
"capabilities": ["integration", "api-testing", "contract-testing"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "E2E Tester",
"capabilities": ["e2e", "ui-testing", "user-flows"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Performance Tester",
"capabilities": ["load-testing", "stress-testing", "benchmarking"]
})
mcp__claude-flow__agent_spawn({
"type": "monitor",
"name": "Security Tester",
"capabilities": ["security-testing", "penetration-testing", "vulnerability-scanning"]
})
Test Coverage
Coverage Analysis
// Quality assessment
mcp__claude-flow__quality_assess({
"target": "test-coverage",
"criteria": ["line-coverage", "branch-coverage", "function-coverage"]
})
// Edge case detection
mcp__claude-flow__pattern_recognize({
"data": testScenarios,
"patterns": ["edge-case", "boundary-condition", "error-path"]
})
Test Execution
// Parallel test execution
mcp__claude-flow__parallel_execute({
"tasks": [
{ "id": "unit-tests", "command": "npm run test:unit" },
{ "id": "integration-tests", "command": "npm run test:integration" },
{ "id": "e2e-tests", "command": "npm run test:e2e" }
]
})
// Batch processing for test suites
mcp__claude-flow__batch_process({
"items": testSuites,
"operation": "execute-test-suite"
})
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 · 143 lines · 15 tokens per session scan A e298572ac0f7
source-command-swarm-testing 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 819 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
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
nguyen-ly-test-file-tach-biet
(Use when) Dùng khi cần tạo, review, hoặc tổ chức cấu trúc test file (unit, component) theo mô hình tách biệt 100% khỏi mã nguồn sản phẩm (Electron/Desktop/Frontend), hoặc theo Go convention (test.go cùng package). Bao gồm fixtures, path aliases, build isolation, phân định rõ giữa electron/test/ (nội bộ) với…
test-cases
Generate test cases from a Jira ticket's acceptance criteria. Produces e2e test scenarios (steps and expected results, no code) and a unit test checklist for developers. Test cases map back to requirements for traceability. Use when: "write test cases", "generate tests", "e2e tests for PROJ-789", "test cases for this…
verification-traceability
Make a declared design assertion checkable and traceable. Use when adding or changing a contract assertion, choosing how to verify a behaviour, or when a behaviour has no expected output.
cometchat-ios-testing
Test an iOS app that embeds CometChat — what to mock vs exercise for real, keeping the CometChatSDK off the network in unit tests, waiting out the async init→login gate, and a lean XCUITest smoke. Triggers: 'test cometchat ios', 'unit test chat swift', 'mock cometchatsdk', 'xcuitest for chat', 'how do I test cometchat…
loom-testing
Test implementation across unit, integration, e2e, security, infrastructure, data pipeline, and ML domains.