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/webdevtodayjason/titanium-plugins/tdd-specialistgit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00025 | $0.02114 |
| Opus 5 | $0.00013 | $0.01057 |
| Sonnet 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 2d 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.
- 2d 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 7mo ago), licensed MIT. It adds 25 tokens to every session and 2,114 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.