agent-tdd-london-swarm

agent-tdd-london-swarm is a skill for Claude Code from Soulcynics404/AgentForge. It costs 28 tokens per session (1,567 once invoked), scanned A, a copy of agent-tdd-london-swarm, MIT.

A testing skill based on the London School of Test-Driven Development, or TDD, where tests use mocks to describe how parts of a program collaborate. Mocks and stubs are test replacements for real components.

In plain words
What is it for?
Use it for outside-in TDD, mock-driven tests, checking object interactions, and coordinating tests across an agent swarm.
Why use it?
It helps developers design behavior and interactions before implementation while isolating each part of the system.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the claude-flow plugin — 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server shipped together

Good fit Use it for outside-in TDD, mock-driven tests, checking object interactions, and coordinating tests across an agent swarm.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/soulcynics404/agentforge/agent-tdd-london-swarm
Install

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.

Any agent
npx skills add Soulcynics404/AgentForge --skill agent-tdd-london-swarm
Clone the repo
git clone --depth 1 https://github.com/Soulcynics404/AgentForge

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server.

Wrote 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.

agentmods badge for agent-tdd-london-swarm

README.md
[![agentmods](https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-tdd-london-swarm/github.svg)](https://agentmods.dev/skills/soulcynics404/agentforge/agent-tdd-london-swarm)
Your own site
<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/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.

agentmods 80×15 button for agent-tdd-london-swarm

Your own site · 80×15
<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-tdd-london-swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,567 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 192b64f17131, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

Origin

This is a copy

100% identical to agent-tdd-london-swarm — 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.

.agents/skills/agent-tdd-london-swarm/SKILL.md · 249 lines

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

  1. Outside-In TDD: Drive development from user behavior down to implementation details
  2. Mock-Driven Development: Use mocks and stubs to isolate units and define contracts
  3. Behavior Verification: Focus on interactions and collaborations between objects
  4. Swarm Test Coordination: Collaborate with other testing agents for comprehensive coverage
  5. 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);
  });
});

Read the full file on GitHub · 249 lines

Changes

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.

  1. 8d ago First seen · 249 lines · 28 tokens per session scan A 192b64f17131

Subscribe to this mod's changes

agent-tdd-london-swarm is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 19d ago), 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. It is 100% identical to agent-tdd-london-swarm, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

taiyi-dev

A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.

Dong90/oh-my-taiyiforge · 21 tokens

spec-driven-development

Design and run a Spec-Driven Development (SDD) pipeline for AI software factories — where structured specifications are the input, AI agents generate the code, and quality gates enforce correctness at each phase: SPECIFY → DECOMPOSE → IMPLEMENT → VERIFY → DELIVER. Use when building or refining a spec-driven pipeline…

magnus919/agent-skills · 165 tokens

tdd

A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.

Insajin/autopus-adk · 11 tokens

debugging

A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.

Insajin/autopus-adk · 16 tokens

test-driven-development

Use tests to define the target behavior before changing implementation.

aaronnat23/disp8ch · 0 tokens

代码调试

A debugging workflow that reproduces a problem with a failing test, collects evidence, finds the underlying cause, applies a fix, and runs regression checks. Regression checks verify that the fix does not break behavior that already worked.

jianchen08/Agent-os-open · 82 tokens