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.
git clone --depth 1 https://github.com/adilkalam/orcaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/adilkalam/orca/nextjs)<a href="https://agentmods.dev/commands/adilkalam/orca/nextjs"><img src="https://agentmods.dev/badge/commands/adilkalam/orca/nextjs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/adilkalam/orca/nextjs"><img src="https://agentmods.dev/badge/commands/adilkalam/orca/nextjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00014 | $0.09051 |
| Opus 5.5 | $0.00006 | $0.03620 |
| Sonnet 5.5 | $0.00003 | $0.01810 |
| Haiku 4.5 | $0.00001 | $0.00905 |
Grade A, and why
nextjs 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 2mo 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 — 886 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP - DELEGATION ONLY
Before you do ANYTHING else, read this.
This slash command EXISTS to delegate work to agents. Not to do work directly.
NEVER acceptable:
- "This is simple, I'll just do it directly"
- "Let me quickly fix this"
- "I can handle this without agents"
- Using Edit/Write tools to make changes yourself
ALWAYS required:
- Parse the arguments
- Determine routing (--tweak, default, --complex)
- Spawn specialists single-level via the
Agenttool (you are the orchestrator, in the main thread — no orchestrator subagent; OS 7.1)
Even --tweak delegates to a builder. It skips gates, not agents.
If you are about to Edit/Write, STOP. Delegate instead.
/nextjs - Next.js Lane Orchestrator (OS 7.1)
Use this command for Next.js / React frontend UI work (App Router, RSC, TypeScript, semantic CSS).
Flat pattern: this command runs in the main thread and IS the orchestrator. It spawns
the 8 real nextjs agents single-level via Agent(): nextjs-architect (planning /
analysis), nextjs-builder (implementation — owns CSS / layout / tokens),
nextjs-standards-enforcer (standards gate), nextjs-verification-agent (verification),
and the specialists nextjs-typescript-specialist, nextjs-performance-specialist,
nextjs-accessibility-specialist, nextjs-seo-specialist. Design adjudication for
UI-affecting tasks is the shared web design lane floor (design-validator + the
designcheck detector, docs/reference/design-lane.md) — there are no CSS / layout /
design-review specialist agents; that work is owned by the builder + the design floor.
See docs/pipelines/nextjs-pipeline.md and docs/reference/phase-configs/nextjs-phase-config.yaml.
Usage
/nextjs "update the pricing page layout" # Default: light path + gates
/nextjs --tweak "fix button spacing" # Fast: light path, no gates
/nextjs --complex "multi-page feature" # Full: architect + builder + all gates
/nextjs "implement requirement 2025-11-25-0930-dashboard" # Full path with spec
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.
- 2mo ago First seen · 886 lines · 14 tokens per session scan A 057c4ddf9b4b
nextjs is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 20d ago), licensed MIT. It adds 14 tokens to every session and 9,051 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
story-and-test
For the component(s) in scope.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.