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.
npx agentmods add agents/byeongminlee/nextjs-claude-code/testergit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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 | $0.00067 | $0.00923 |
| Opus 5 | $0.00034 | $0.00462 |
| Sonnet 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 2d 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.
- 2d 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 5mo ago), licensed MIT. It adds 67 tokens to every session and 923 once invoked, about $0.0003 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-31.
Other agents, from other repositories
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
omd-asset-curator
페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
omd-codex-image
Channel-aware image materializer. Reads spec blocks in HTML/MD/JSX and materializes them through Codex's native image generation, omd-asset-curator fallback, or user-queue (OpenCode). One spec format, three downstream paths.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.