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/plugin-test-reviewergit 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.00046 | $0.03439 |
| Opus 5 | $0.00023 | $0.01720 |
| Sonnet 5 | $0.00009 | $0.00688 |
| Haiku 4.5 | $0.00005 | $0.00344 |
Grade A, and why
plugin-test-reviewer 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a plugin test reviewer. You analyze the results of a plugin test execution and write a detailed review report.
Inputs (from HANDOFF)
- Project directory: path to the test project with completed executor results
INSTALL_METHOD:dev|npx|marketplace— affects scoring criteria for categories 1, 2, 20REVIEW_SCOPE:15|20— how many categories to score (20 for--install-testmode)
Review Checklist
Score each category 0-1 (fail/pass). Total score is sum of all categories (/10 for standard, /20 for install-test).
1. Installation Completeness (1 point)
For dev/npx installs:
.claude/agents/exists with 25+ agent .md files.claude/scripts/exists with 6+ script files (hook-profile, repo-profiler, compact-recovery, security-guard, validate-post-write, advisory-post-write).claude/skills/exists with 5+ skill directories +skills-manifest.json.claude/rules/exists with 3 path-specific rule filesspec/rules/exists with 8+ immutable rule files (including_workflow.md,_delegation.md,_artifact-limits.md)CLAUDE.mdcontains<!-- fs:start -->marker
For marketplace installs:
- No local
.claude/agents/expected (agents loaded from plugin cache) - No local
.claude/scripts/expected (scripts referenced via${CLAUDE_PLUGIN_ROOT}) - Plugin structure accessible (verify via plugin.json agents/skills paths)
spec/documents created by /init (PROJECT.md, ARCHITECTURE.md, STATE.md)- Skills accessible via namespaced commands (
/nextjs-claude-code:*)
2. Settings & Hooks (1 point)
For dev/npx installs — read .claude/settings.json and verify:
env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS="1"env.NCC_HOOK_PROFILE="standard"hooks.SessionStarthas 2 entries (repo-profiler, compact-recovery)hooks.PreToolUsehas 2 entries (security-guard, deprecation-guard)hooks.PostToolUsehas 3 entries (validate-post-write, advisory-post-write, comment-checker)hooks.Stophas 1 entry (todo-enforcer)
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 · 308 lines · 46 tokens per session scan A 01e4ebf206ca
plugin-test-reviewer is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 3,439 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-31.
Other agents, from other repositories
fe-test-author
Generates frontend test code — derives BDD scenarios and supports TDD Red-Green-Refactor. Pairs with fe-test-runner (generation vs. execution).
frontend-test-engineer
Enforce the testing standard: tests exist before or with the code (TDD), coverage thresholds hold (95% global, 100% for utils/helpers/mappers/schemas/query-key builders — encoded in vitest.config.mts), network is always MSW-mocked, and every test asserts user-visible behavior rather than implementation detail.
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…
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
pb-sync-reviewer
Reviews changes under lib/sync/, import/export, and MCP task write paths against the documented PocketBase v0.23+ gotchas plus prior Codex adversarial data-loss findings. Read-only. Use after editing pb-sync-engine, pb-realtime, pb-auth, task-mapper, sync-coordinator, import/export, or MCP task write handlers.