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 skills/byeongminlee/nextjs-claude-code/plugin-testnpx skills add ByeongminLee/nextjs-claude-code --skill plugin-testgit 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.00070 | $0.02711 |
| Opus 5 | $0.00035 | $0.01355 |
| Sonnet 5 | $0.00014 | $0.00542 |
| Haiku 4.5 | $0.00007 | $0.00271 |
Grade A, and why
plugin-test 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plugin-test — NCC Plugin E2E Test Suite
Usage
/plugin-test # Interactive — suggest a test mode based on recent changes
/plugin-test --quick # Phase 1 only: 4 diverse projects × 4 features each
/plugin-test --full # Phase 1 + Phase 2: full suite including monorepo + cross-feature mods
/plugin-test --install-test # Install test: 2 projects (npx + marketplace), 5 features each, non-spec-dev focus
/plugin-test --phase1 # Phase 1 only (same as --quick)
/plugin-test --phase2 # Phase 2 only: 10-feature monorepo (solo + team)
/plugin-test --security # Security-focused: run security-reviewer on all generated code
/plugin-test --a11y # Accessibility-focused: run browser-tester a11y checks on UI projects
/plugin-test --codequality # Code quality audit: deep analysis of all generated source files
/plugin-test --token # Token optimization audit: run token-optimizer on plugin source
/plugin-test healthcare,marketplace # Run specific projects only
/plugin-test --create # /create pipeline test: new + existing project ideation
Test Modes
Phase 1: Quick Validation (--quick, --phase1)
4 diverse projects, each with 4 features + extra agent verification.
| Project | Stack | Extra Agents |
|---|---|---|
healthcare |
Prisma + next-auth + zod + vitest | /security, /review |
design-system |
framer-motion + playwright + storybook | browser-tester, /qa --a11y |
realtime-collab |
drizzle + tanstack-query + zustand + msw | performance-optimizer, /loop |
marketplace |
Prisma + stripe + ai-sdk + @vercel/blob | /security --diff, /review, /status |
Per-project: NCC install → /init → 4× spec→dev (3 tasks each) → extra agent runs → TEST_LOG.md
Reviewer scores 15 categories: 1-10: Installation, Hooks, Skills, Spec, Design, PLAN, TDD, Token, Code, Flow 11: Rules size (<200 lines each) 12: Skill selection accuracy (manifest vs package.json) 13: Extra agent execution results 14: Document sync (CONTEXT.md/design.md consistency) 15: Code quality detail (error handling, Zod, composition, Server/Client)
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 198 lines · 70 tokens per session scan A 896908568d76
plugin-test is a skill published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 2,711 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 skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
rebase-themes
Rebase all theme- branches onto main, resolving conflicts while preserving each theme's visual identity. Force-pushes directly to theme branches with backup tags. Run as a scheduled task or one-off.
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.