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/icoretech/airbroke/nextjs-16git clone --depth 1 https://github.com/icoretech/airbrokeWrote 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/agents/icoretech/airbroke/nextjs-16)<a href="https://agentmods.dev/agents/icoretech/airbroke/nextjs-16"><img src="https://agentmods.dev/badge/agents/icoretech/airbroke/nextjs-16.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
nextjs-16 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 3d 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.
What it actually says
Next.js 16
Repo Contracts
- App Router project with route handlers under
app/api/** typedRoutes: truereactCompiler: truecacheComponents: trueoutput: "standalone"serverExternalPackages:@airbrake/node,@sentry/node
Routing and API Compatibility
- Preserve the compatibility rewrites and redirects in
next.config.tswhen moving or renaming collectors and notice or occurrence pages - When using
redirect()in server code, remember it throws intentionally - If a
try/catchmust coexist with redirects, rethrow redirect errors or keep the redirect outside thetry
Server Actions and Revalidation
- Follow the existing pattern in
lib/actions/*: validate input, mutate through Prisma, revalidate tags or paths, thenrefresh()orredirect()as needed - Use
unstable_rethrowwhen catching errors around redirecting server actions so Next control flow is preserved - If a mutation changes server-rendered UI, refresh or revalidate the canonical server path instead of relying only on optimistic local state
Auth and Build-Time Safety
lib/auth.tsuses lazy Better Auth initialization on purpose sonext builddoes not require auth runtime env just to import the module- Preserve that lazy pattern when changing auth wiring or provider logic
- Keep server-only auth, Prisma, and collector code out of client bundles
Build Rules
- Run builds inside the
webcontainer - Always set
NODE_ENV=productionexplicitly for production build verification - Standalone output is the deployable artifact, so check
.next/standaloneimplications before changing Docker copy steps or runtime file access
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A 34ec97208ad4
nextjs-16 is an agent published in the GitHub repository icoretech/airbroke (222 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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-30.
Other agents, from other repositories
software-engineer
Implements Accepted specs end to end, fixes bugs, and refactors without changing behaviour. Use proactively for new features once the spec is Accepted, domain/Prisma/Server Action changes, and technical approach decisions. Do not use when the request is a problem without a spec — that is product-manager.
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
domain-architect
Designs domain rules, invariants and pure function contracts before implementation. Use proactively for new features with non-trivial rules, ambiguous or conflicting requirements, calculations and state machines, inconsistencies between a spec and the code, or when deciding what belongs in domain versus services.
ui-ux-developer
Designs and builds product interfaces — screens, layouts, forms, sheets, tables, dashboards, empty and error states. Use proactively when creating or refining any user-facing surface, or auditing an existing one.