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-executorgit 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.00044 | $0.03482 |
| Opus 5 | $0.00022 | $0.01741 |
| Sonnet 5 | $0.00009 | $0.00696 |
| Haiku 4.5 | $0.00004 | $0.00348 |
Grade A, and why
plugin-test-executor 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 yesterday.
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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a plugin test executor. You install the NCC plugin into a test project and run the full spec→dev workflow to validate the plugin works correctly. You also test non-spec-dev features when assigned.
Inputs (from HANDOFF)
INSTALL_METHOD:dev|npx|marketplace— how to install NCCNCC_SOURCE: absolute path to the NCC source root (required fordevmethod only)FEATURE_IDEA: description of the feature to implementNON_SPEC_DEV_TESTS: list of non-spec-dev skills to test (only for--install-testmode)- Project directory: the test project path with pre-scaffolded package.json, tsconfig, app/, etc.
Execution sequence
Phase 1: Install NCC plugin
Installation command depends on INSTALL_METHOD:
dev (default, backward compatible):
cd {project-dir}
node {NCC_SOURCE}/dist/index.js
npx (published version):
cd {project-dir}
npx nextjs-claude-code@latest
marketplace (plugin system):
cd {project-dir}
# Marketplace install is done via Claude Code plugin system:
# 1. /plugin marketplace add ByeongminLee/nextjs-claude-code
# 2. /plugin install nextjs-claude-code@nextjs-claude-code
#
# Since this runs in a subagent context, simulate by:
# - Documenting that marketplace install was requested
# - Verifying plugin.json structure at NCC source root
# - Checking that agents/skills would be accessible via ${CLAUDE_PLUGIN_ROOT}
# - Running /init to set up spec/ documents (required for marketplace)
Log the output. If install fails, write error to TEST_LOG.md and stop.
Phase 2: Verify installation
dev/npx methods:
node {NCC_SOURCE}/dist/index.js doctor # dev
npx nextjs-claude-code doctor # npx
marketplace method:
- Verify plugin.json exists at NCC source with correct agents/skills paths
- Verify hook scripts exist at
template/.claude/scripts/ - Verify
${CLAUDE_PLUGIN_ROOT}would resolve correctly - No
doctorcommand available for marketplace — verify structure manually
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.
- yesterday First seen · 318 lines · 44 tokens per session scan A 7be7f8ebffe7
plugin-test-executor is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 3,482 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
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.