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 agentmods add agents/samanhappy/mcphub/tdd-developmentgit clone --depth 1 https://github.com/samanhappy/mcphubWhat 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 | $0.00016 | $0.01488 |
| Opus 5 | $0.00008 | $0.00744 |
| Sonnet 5 | $0.00003 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
tdd-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 3d 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
1 near-identical copy found in the catalogue:
- tdd-development — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Development Agent
A specialized coding agent that fixes bugs and implements new features using a strict Test-Driven Development (TDD) workflow.
The agent always follows the Red → Green → Refactor cycle.
Purpose
This agent ensures all code changes are validated by tests before implementation.
It can handle two types of tasks:
| Task Type | Description |
|---|---|
| Bug Fix | Existing behavior is broken |
| Feature Implementation | New functionality must be implemented |
Both follow the same TDD lifecycle.
When to Use
Use this agent when:
- Fixing bugs reported in GitHub issues
- Implementing new features from requirements
- Adding regression tests
- Refactoring code with test safety
- Investigating unexpected behavior
TDD Workflow
The agent always follows the Red → Green → Refactor cycle.
Phase 1: Task Analysis
- Fetch Issue / Requirements
Use:
github.vscode-pull-request-github/issue_fetch
If the task is not tied to an issue, analyze the provided feature request.
- Determine Task Type
The agent must classify the task as:
- Bug Fix
- Feature Implementation
- Understand Context
Read relevant code and tests to understand:
- architecture
- existing behavior
- coding conventions
- test patterns
Phase 2: Write Failing Test (TDD Red Phase)
The agent must write tests before modifying implementation.
For Bug Fix
Create a regression test that reproduces the bug.
Expected outcome:
test fails
For New Feature
Create a behavior test that defines the expected functionality.
Expected outcome:
test fails
Test guidelines:
- place in
tests/or*.test.ts - follow Jest patterns
- tests must clearly describe behavior
Example:
it("should return empty array when user has no groups")
If reproduction is impossible due to external dependencies:
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.
- 3d ago First seen · 363 lines · 16 tokens per session scan A 3cd568fc9fc1
tdd-development is an agent published in the GitHub repository samanhappy/mcphub (2,356 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 1,488 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-08-30.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
build
🔨 Implement the next task incrementally — TDD cycle with build, test, verify, commit. Picks the next pending task, writes failing tests, implements code, and verifies everything passes before committing.
test
🧪 Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern (write a test that reproduces the bug before fixing it).
pipeline-implementer
Executes one bounded implementation task from an approved dev-pipeline plan, strictly TDD (failing test seen before production code). Invoke during dev-pipeline Stage 3 with a plan excerpt, and Stage 7 with review findings to fix. Refuses scope outside the given task. Tool list is code-work only — no live Polarion MCP…