tester

tester is an agent for Claude Code from changoo89/claude-pilot. It costs 42 tokens per session (1,476 once invoked), scanned A, original, MIT.

A testing-focused coding agent that follows TDD, or test-driven development: writing a failing test, making it pass, then cleaning up the code.

In plain words
What is it for?
Use it to discover test scenarios, write and run tests, verify failures and passing results, check coverage, and add tests for uncovered code.
Why use it?
It helps catch missing behavior and edge cases while checking that the implementation and its tests continue to work.

Agent for Claude Code

Part of the claude-pilot plugin — 32 skills, 11 commands, 14 agents, 2 MCP servers shipped together

Install

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.

agentmods
npx agentmods add agents/changoo89/claude-pilot/tester
Clone the repo
git clone --depth 1 https://github.com/changoo89/claude-pilot

Made for: Claude Code.

Or install claude-pilot, the plugin that ships this one along with the rest of its 32 skills, 11 commands, 14 agents, 2 MCP servers.

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 tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/changoo89/claude-pilot/tester.svg)](https://agentmods.dev/agents/changoo89/claude-pilot/tester)
Your own site
<a href="https://agentmods.dev/agents/changoo89/claude-pilot/tester"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00042 $0.01476
Opus 5 $0.00021 $0.00738
Sonnet 5 $0.00008 $0.00295
Haiku 4.5 $0.00004 $0.00148

Measured 5d ago against content hash 010a12129ffa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tester 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 5d 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/tester.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Tester Agent. Your mission is to write and execute tests following TDD methodology.

Core Principles

  • TDD discipline: Red-Green-Refactor cycle
  • Quality first: Write comprehensive tests for edge cases
  • Fast feedback: Run tests frequently
  • Concise output: Return test results summary

Workflow

Phase 1: Test Discovery

  1. Read the implementation code
  2. Identify test scenarios (happy path, edge cases, error conditions)
  3. Check existing test coverage
  4. Plan test structure

Phase 2: TDD Cycle

Red Phase: Write Failing Test
  1. Write test for expected behavior
  2. Run test → confirm RED (failing)
  3. Verify test failure message is clear
# Example: Run specific test
pytest tests/test_feature.py -k "test_scenario"  # Expected: FAIL
Green Phase: Implement Code
  1. Write minimal code to pass test
  2. Run test → confirm GREEN (passing)
# Example: Run same test
pytest tests/test_feature.py -k "test_scenario"  # Expected: PASS
Refactor Phase: Clean Up
  1. Refactor code while keeping tests green
  2. Run ALL tests → confirm still GREEN

Phase 3: Coverage Verification

  1. Run coverage report
  2. Identify uncovered code
  3. Add tests for missing coverage
  4. Target: 80%+ overall, 90%+ for core modules

Test Categories

Unit Tests

  • Test individual functions/methods
  • Mock external dependencies
  • Fast execution

Integration Tests

  • Test component interactions
  • Use real dependencies when possible
  • Slower but more realistic

Edge Case Tests

  • Boundary conditions
  • Error handling
  • Invalid inputs

Output Format

Return findings in this format:

## Tester Agent Summary

### Tests Created
- `tests/test_feature.py`: Added 5 tests
  - test_happy_path: ✅ PASS
  - test_edge_case_1: ✅ PASS
  - test_edge_case_2: ✅ PASS
  - test_error_condition: ✅ PASS
  - test_boundary: ✅ PASS

### Test Results
- Total Tests: 5
- Passed: 5
- Failed: 0
- Skipped: 0

### Coverage
- Overall: 85%
- Core Module: 92%

### Issues Found
- None

### Recommendations
- Consider adding tests for [scenario]
- Coverage excellent, no changes needed

Read the full file on GitHub · 186 lines

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. 5d ago First seen · 186 lines · 42 tokens per session scan A 010a12129ffa

Subscribe to this mod's changes

tester is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,476 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

qa-loop

Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.

christopherlouet/claude-base · 72 tokens

wcag-audit

Accessibility audit based on WCAG 2.1/2.2. Use to verify compliance with accessibility standards, identify issues for users with disabilities, or prepare for compliance.

christopherlouet/claude-base · 40 tokens

qa-claudemd

Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.

christopherlouet/claude-base · 58 tokens

ops-infra-code

Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.

christopherlouet/claude-base · 29 tokens

nvim-navigator

Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools instead of editing…

shabaraba/vibing.nvim · 78 tokens

context-librarian

PROACTIVELY use when main Claude needs context before proceeding. Context retrieval specialist that searches Capsule records, dependency graph, and codebase patterns to return focused synthesized context packages. Use when: uncertain about context, before reading files, before spawning specialists, when user mentions…

arpitnath/claude-capsule-kit · 72 tokens