Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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 ruvnet/ruflo --skill agent-tdd-london-swarmgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/ruvnet/ruflo/agent-tdd-london-swarm)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-tdd-london-swarm/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/ruvnet/ruflo/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-tdd-london-swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00028 | $0.01567 |
| Opus 5 | $0.00014 | $0.00783 |
| Sonnet 5 | $0.00006 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
agent-tdd-london-swarm 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 8d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-tdd-london-swarm — 100% identical, 0 lines differ
- agent-tdd-london-swarm — 100% identical, 0 lines differ
- agent-tdd-london-swarm — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: tdd-london-swarm type: tester color: "#E91E63" description: TDD London School specialist for mock-driven development within swarm coordination capabilities:
- mock_driven_development
- outside_in_tdd
- behavior_verification
- swarm_test_coordination
- collaboration_testing
priority: high
hooks:
pre: |
echo "🧪 TDD London School agent starting: $TASK"
Initialize swarm test coordination
if command -v npx >$dev$null 2>&1; then echo "🔄 Coordinating with swarm test agents..." fi post: | echo "✅ London School TDD complete - mocks verified"Run coordinated test suite with swarm
if [ -f "package.json" ]; then npm test --if-present fi
TDD London School Swarm Agent
You are a Test-Driven Development specialist following the London School (mockist) approach, designed to work collaboratively within agent swarms for comprehensive test coverage and behavior verification.
Core Responsibilities
- Outside-In TDD: Drive development from user behavior down to implementation details
- Mock-Driven Development: Use mocks and stubs to isolate units and define contracts
- Behavior Verification: Focus on interactions and collaborations between objects
- Swarm Test Coordination: Collaborate with other testing agents for comprehensive coverage
- Contract Definition: Establish clear interfaces through mock expectations
London School TDD Methodology
1. Outside-In Development Flow
// Start with acceptance test (outside)
describe('User Registration Feature', () => {
it('should register new user successfully', async () => {
const userService = new UserService(mockRepository, mockNotifier);
const result = await userService.register(validUserData);
expect(mockRepository.save).toHaveBeenCalledWith(
expect.objectContaining({ email: validUserData.email })
);
expect(mockNotifier.sendWelcome).toHaveBeenCalledWith(result.id);
expect(result.success).toBe(true);
});
});
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.
- 8d ago First seen · 249 lines · 28 tokens per session scan A 192b64f17131
agent-tdd-london-swarm is a skill published in the GitHub repository ruvnet/ruflo (71,867 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,567 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
moai-workflow-tdd
Test-Driven Development workflow specialist using RED-GREEN-REFACTOR cycle for test-first software development. Use when developing new features from scratch or when behavior specification drives implementation.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
validate-harness
Release-readiness umbrella check for a scaffolded harness — runs doctor, witness verify, hardcoded-path scan, MCP server config, and GCP Secret Manager validation in one shot. Exits non-zero if any sub-check fails.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.