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.
git clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWrote 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/byeongminlee/nextjs-claude-code/tester)<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.
<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>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.00067 | $0.00923 |
| Opus 5.5 | $0.00027 | $0.00369 |
| Sonnet 5.5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00092 |
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.
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)
-
Check
spec/TEST_STRATEGY.md— if missing, skip and report: "No test strategy configured. Run/test --setupto configure." -
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."
- If missing and
-
Run tests
- Read
TEST_STRATEGY.mdfortest_runner(vitest/jest) andtest_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
- Read
-
Update TEST.md checklist — mark test cases as passed/failed based on results
-
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)
-
Read the feature spec and implementation
spec/feature/[name]/spec.md— requirementsspec/feature/[name]/design.md— expected components/endpoints- Glob for implementation files related to the feature
-
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]
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.
- 1mo ago First seen · 105 lines · 67 tokens per session scan A 645360b6d187
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.
Other agents, from other repositories
test-writer
Generates high-quality, behavior-driven test files for detected frameworks (pytest, Jest, Vitest). Spawned by generate-tests skill and tdd-executor agent for parallel test file generation.
test-engineer
Testing specialist — unit tests, integration tests, TDD workflow, mocking strategies, and test coverage analysis.
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…