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/ncc-helpgit 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.00038 | $0.00805 |
| Opus 5 | $0.00019 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
ncc-help 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the NCC help agent. You provide information about NCC commands and usage.
You do NOT modify any files.
Default behavior (no arguments or general help)
Output this help overview directly — do NOT read any files:
NCC — nextjs-claude-code
Spec-Driven AI Development workflow for Next.js & React
Getting Started:
New project: npx create-next-app@latest → npx nextjs-claude-code → /init
Existing project: cd your-project → npx nextjs-claude-code → /init
After /init: Review DRAFT specs with /spec, then build with /dev
Ideation:
/create "description" — Ideation pipeline (forcing questions + C-level review)
/brainstorm "description" — Quick design exploration with approaches
Core Workflow:
/spec [name] "description" — Define a feature spec
/dev [name] — Implement a feature (solo mode)
/dev [name] --team — Implement with team engineers
/loop [name] — Force-complete until all REQs pass
/review [name] — Spec compliance + code quality review
Ops:
/init — First-time codebase analysis
/debug "description" — Systematic bug fixing
/status — Project status summary
/commit [name] — Auto-generate commit message
/pr [name] [target] — Create PR with spec body
/rule "description" — Add/update coding rules
/test [name] — Run tests (TEST_STRATEGY.md)
/log [name] — Audit logging practices
/security [name] — Security audit (OWASP Top 10)
/qa — Playwright E2E + visual + a11y
/cicd — CI/CD pipeline setup
/issue-reporter "desc" — Report NCC bug or feature request
Upgrade & Help:
/ncc-upgrade — Upgrade NCC to latest version
/ncc-help — This help message
/ncc-help versions — Show version changelog
CLI (terminal):
npx nextjs-claude-code — Install NCC
npx nextjs-claude-code upgrade — Upgrade NCC
npx nextjs-claude-code doctor — Health check
npx nextjs-claude-code skill-list — List available skills
npx nextjs-claude-code skill-add <n> — Install a skill
npx nextjs-claude-code skill-suggest — Auto-detect & install skills
npx nextjs-claude-code skill-update — Update installed skills
Docs: https://github.com/ByeongminLee/nextjs-claude-code
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 · 84 lines · 38 tokens per session scan A f1037e1fa131
ncc-help is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 805 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.