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 proffesor-for-testing/agentic-qe --skill agent-tdd-london-swarmgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-tdd-london-swarm)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/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/proffesor-for-testing/agentic-qe/agent-tdd-london-swarm"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-tdd-london-swarm.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.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.
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.
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 proffesor-for-testing/agentic-qe (475 stars, last pushed 4d 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.
Other skills, from other repositories
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
create-tooluniverse-skill
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
drill-tdd
Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first.
the-hit
Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols.