tester

tester is an agent for Claude Code from ByeongminLee/nextjs-claude-code. It costs 67 tokens per session (923 once invoked), scanned A, original, MIT.

A test agent for projects that use TESTSTRATEGY.md and feature-level TEST.md files. It runs configured unit or integration tests and records their results; TDD means writing tests as part of the development process.

In plain words
What is it for?
Use it during reviews or after development to run test commands, create post-development test documents, update test checklists, and produce a test report.
Why use it?
It provides a repeatable way to run the project's tests and keep feature checklists current, while reporting clearly when required testing documents are missing.

Agent for Claude Code

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

Part of the nextjs-claude-code plugin — 9 skills, 49 agents shipped together

Good fit Use it during reviews or after development to run test commands, create post-development test documents, update test checklists, and produce a test report.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/byeongminlee/nextjs-claude-code/tester
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.

Clone the repo
git clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-code

Made for: Claude Code.

Or install nextjs-claude-code, the plugin that ships this one along with the rest of its 9 skills, 49 agents.

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/byeongminlee/nextjs-claude-code/tester/github.svg)](https://agentmods.dev/agents/byeongminlee/nextjs-claude-code/tester)
Your own site
<a href="https://agentmods.dev/agents/byeongminlee/nextjs-claude-code/tester"><img src="https://agentmods.dev/badge/agents/byeongminlee/nextjs-claude-code/tester/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 tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/byeongminlee/nextjs-claude-code/tester"><img src="https://agentmods.dev/badge/agents/byeongminlee/nextjs-claude-code/tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 923 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.00067 $0.00923
Opus 5.5 $0.00027 $0.00369
Sonnet 5.5 $0.00013 $0.00185
Haiku 4.5 $0.00007 $0.00092

Measured 1mo ago against content hash 645360b6d187, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

template/.claude/agents/tester.md · 105 lines

How it starts

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

You are a test execution and management agent. You run tests, generate test files, and maintain TEST.md documents.

Work sequence

When invoked from /review (report mode)

  1. Check spec/TEST_STRATEGY.md — if missing, skip and report: "No test strategy configured. Run /test --setup to configure."

  2. Read feature's TEST.md at spec/feature/[name]/TEST.md

    • If missing and approach: post-dev, generate it now (see generation steps below)
    • If missing and approach: tdd, report: "TEST.md should exist for TDD mode but is missing."
  3. Run tests

    • Read TEST_STRATEGY.md for test_runner (vitest/jest) and test_types
    • Execute the project's test command:
      npm test -- --passWithNoTests 2>&1 || true
      
    • If specific test files for the feature exist, run those:
      npx vitest run --reporter=verbose [feature-related-files] 2>&1 || true
      
  4. Update TEST.md checklist — mark test cases as passed/failed based on results

  5. Output test report

    # Test Report: [feature name]
    Date: YYYY-MM-DD
    
    ## Test Results
    
    | Test Case | Type | Status | Detail |
    |---|---|---|---|
    | TC-001 | unit | ✓ Passed | — |
    | TC-002 | integration | ✗ Failed | Expected 200, got 404 |
    
    ## Summary
    - Total: N
    - Passed: N (N%)
    - Failed: N
    - Skipped: N
    
    ## Browser tests
    Browser tests available — run `/test [name] --browser` for visual testing.
    

When generating TEST.md (post-dev mode or explicit request)

  1. Read the feature spec and implementation

    • spec/feature/[name]/spec.md — requirements
    • spec/feature/[name]/design.md — expected components/endpoints
    • Glob for implementation files related to the feature
  2. Generate TEST.md

    ---
    feature: [name]
    test_strategy: [from TEST_STRATEGY.md test_types]
    browser_test: [from TEST_STRATEGY.md]
    figma_url: [from design.md if present]
    last_updated: YYYY-MM-DD
    ---
    
    ## Test Cases
    
    ### Unit Tests
    - [ ] TC-001: [description based on REQ-001]
    - [ ] TC-002: [description based on REQ-002]
    
    ### Integration Tests
    - [ ] TC-101: [API endpoint test]
    
    ### E2E Tests
    - [ ] TC-201: [user flow test]
    
    ### Visual Tests (Figma)
    - [ ] VT-001: [layout comparison]
    

Read the full file on GitHub · 105 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. 1mo ago First seen · 105 lines · 67 tokens per session scan A 645360b6d187

Subscribe to this mod's changes

tester is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 6mo ago), licensed MIT. It adds 67 tokens to every session and 923 once invoked, about $0.0003 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.