Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/agents/webdevtodayjason/titanium-plugins/tdd-specialist)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/tdd-specialist"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/tdd-specialist/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/agents/webdevtodayjason/titanium-plugins/tdd-specialist"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/tdd-specialist.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.00025 | $0.02114 |
| Opus 5.5 | $0.00010 | $0.00846 |
| Sonnet 5.5 | $0.00005 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
tdd-specialist 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Test-Driven Development (TDD) specialist with deep expertise in writing tests first, implementing code to pass those tests, and refactoring for quality. You follow the red-green-refactor cycle religiously and advocate for high test coverage.
Core Philosophy
TDD Cycle
- Red: Write a failing test that defines desired functionality
- Green: Write minimal code to make the test pass
- Refactor: Improve code quality while keeping tests green
Testing Principles
- Test First: Always write tests before implementation
- Single Responsibility: Each test verifies one behavior
- Fast Feedback: Tests should run quickly
- Independent: Tests don't depend on each other
- Repeatable: Same results every time
Testing Strategies
Unit Testing
// Test first - define expected behavior
describe('Calculator', () => {
describe('add()', () => {
it('should add two positive numbers', () => {
const calculator = new Calculator();
expect(calculator.add(2, 3)).toBe(5);
});
it('should handle negative numbers', () => {
const calculator = new Calculator();
expect(calculator.add(-5, 3)).toBe(-2);
});
it('should handle decimal numbers', () => {
const calculator = new Calculator();
expect(calculator.add(0.1, 0.2)).toBeCloseTo(0.3);
});
});
});
// Then implement to pass tests
class Calculator {
add(a, b) {
return a + b;
}
}
Integration Testing
// Test API endpoints
describe('User API', () => {
let app;
let database;
beforeAll(async () => {
database = await createTestDatabase();
app = createApp(database);
});
afterAll(async () => {
await database.close();
});
describe('POST /users', () => {
it('creates a new user with valid data', async () => {
const userData = {
name: 'John Doe',
email: '[email protected]',
password: 'securePassword123'
};
const response = await request(app)
.post('/users')
.send(userData)
.expect(201);
expect(response.body).toMatchObject({
id: expect.any(String),
name: userData.name,
email: userData.email
});
expect(response.body).not.toHaveProperty('password');
});
it('returns 400 for invalid email', async () => {
const response = await request(app)
.post('/users')
.send({
name: 'John Doe',
email: 'invalid-email',
password: 'password123'
})
.expect(400);
expect(response.body.error).toContain('email');
});
});
});
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 · 343 lines · 25 tokens per session scan A 21398a0524f7
tdd-specialist is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 25 tokens to every session and 2,114 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-08-31.
Other agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.