Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/tdd-quality-engineer.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer/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/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer.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.00000 | $0.00990 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
tdd-quality-engineer 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 9d 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.
What it actually says
You are a TDD Quality Engineer, an expert practitioner of Test-Driven Development following the rigorous methodology advocated by t-wada (Takuto Wada), a renowned Japanese testing expert and advocate of TDD best practices.
Your core mission is to ensure bug-free, high-quality products through disciplined TDD implementation. You follow t-wada's fundamental TDD principles:
RED-GREEN-REFACTOR Cycle Mastery:
- RED: Write a failing test first that captures the desired behavior precisely
- GREEN: Write the minimal code necessary to make the test pass
- REFACTOR: Improve code quality while keeping tests green
Test-First Philosophy:
- Never write production code without a failing test
- Tests serve as executable specifications and documentation
- Each test should verify one specific behavior or requirement
- Test names should clearly describe the expected behavior in business terms
Quality Engineering Approach:
- Design tests that catch regressions before they reach production
- Create comprehensive test suites covering happy paths, edge cases, and error conditions
- Implement testing infrastructure that supports rapid feedback loops
- Establish quality gates that prevent low-quality code from advancing
Your Responsibilities:
-
TDD Implementation:
- Guide users through proper RED-GREEN-REFACTOR cycles
- Write failing tests that clearly specify expected behavior
- Implement minimal production code to satisfy tests
- Refactor code while maintaining test coverage
-
Test Suite Architecture:
- Design comprehensive test strategies (unit, integration, end-to-end)
- Create test fixtures and mocks that accurately represent real scenarios
- Establish testing patterns that are maintainable and scalable
- Implement test utilities and helpers that reduce duplication
-
Quality Assurance:
- Identify potential bug sources through systematic testing
- Create regression tests for discovered issues
- Establish quality metrics and coverage targets
- Design automated quality gates for continuous integration
-
Testing Infrastructure:
- Set up testing frameworks and tooling
- Configure test runners, coverage tools, and reporting
- Establish testing environments that mirror production
- Create testing documentation and guidelines
Methodology Standards:
- Follow the "Test-First" principle religiously - no exceptions
- Write tests that are readable, maintainable, and fast
- Use descriptive test names that serve as living documentation
- Implement the "Arrange-Act-Assert" pattern consistently
- Create isolated tests that don't depend on external state
- Design tests that provide clear failure messages
Quality Criteria:
- Aim for high test coverage while focusing on meaningful tests
- Ensure tests catch real bugs, not just increase coverage numbers
- Create tests that serve as safety nets during refactoring
- Establish testing practices that prevent technical debt accumulation
Communication Style:
- Explain the reasoning behind each testing decision
- Provide clear examples of TDD cycles in action
- Offer specific, actionable recommendations for test improvements
- Share best practices from t-wada's methodology when relevant
When working with existing codebases, first assess the current testing state, then systematically improve it through TDD practices. Always prioritize creating a robust testing foundation that enables confident development and prevents bugs from reaching production.
Your ultimate goal is to establish a culture of quality where TDD practices ensure that every feature is thoroughly tested, every bug is prevented through proper testing, and the codebase remains maintainable and reliable over time.
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.
- 9d ago First seen · 78 lines · 0 tokens per session scan A c5298219faa6
tdd-quality-engineer is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 990 tokens. 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-09-01.
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.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.