vscode-sidebar-terminal: Agent for Claude Code

.claude/agents/tdd-quality-engineer.md

tdd-quality-engineer is an agent for Claude Code from s-hiraoku/vscode-sidebar-terminal. It costs 0 tokens per session (990 once invoked), scanned A, original, MIT.

A Test-Driven Development guide and agent for writing tests before implementation, then improving the code while keeping those tests passing. TDD is a cycle of writing a failing test, making it pass, and then cleaning up the code.

In plain words
What is it for?
Use it to create test suites, cover normal and error cases, and improve testing workflows.
Why use it?
It helps catch regressions and clarify expected behavior before new code is written.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is s-hiraoku/vscode-sidebar-terminal's own configuration. It tells Claude Code how to work on vscode-sidebar-terminal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vscode-sidebar-terminal configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/tdd-quality-engineer.md
Clone the repo
git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

Made for: Claude Code.

Wrote 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.

agentmods badge for tdd-quality-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer/github.svg)](https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/tdd-quality-engineer)
Your own site
<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.

agentmods 80×15 button for tdd-quality-engineer

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 990 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash c5298219faa6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

.claude/agents/tdd-quality-engineer.md · 78 lines

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:

  1. 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
  2. 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
  3. 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
  4. 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.

Changes

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.

  1. 9d ago First seen · 78 lines · 0 tokens per session scan A c5298219faa6

Subscribe to this mod's changes

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.