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 skills add san-npm/skills-ws --skill nextjs-stackgit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/skills/san-npm/skills-ws/nextjs-stack)<a href="https://agentmods.dev/skills/san-npm/skills-ws/nextjs-stack"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/nextjs-stack/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/skills/san-npm/skills-ws/nextjs-stack"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/nextjs-stack.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.00086 | $0.00479 |
| Opus 5.5 | $0.00034 | $0.00192 |
| Sonnet 5.5 | $0.00017 | $0.00096 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
nextjs-stack 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 1mo 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 Full-Stack Blueprint
This is the integration layer — how the pieces fit, where the seams leak, and the security/serverless gotchas. For deep single-domain work, lean on the sibling skills: stripe-billing (Checkout/portal/webhook lifecycle), auth-implementation (sessions, RBAC, OAuth), postgres-mastery (schema/indexing/pooling), and api-design (REST/route-handler contracts).
Reference guide
Read only the references needed for the current request:
- Stack Overview: references/stack-overview.md
- Scaffolding: references/scaffolding.md
- Auth (Clerk): references/auth-clerk.md
- Database (Prisma): references/database-prisma.md
- API Layer: pick per call site: references/api-layer-pick-per-call-site.md
- State Management (Zustand): references/state-management-zustand.md
- UI (shadcn/ui): references/ui-shadcn-ui.md
- Payments (Stripe): references/payments-stripe.md
- Deployment (Vercel): references/deployment-vercel.md
- Monitoring (Sentry): references/monitoring-sentry.md
- Testing & CI: references/testing-ci.md
- .env.example: references/env-example.md
What ships with it
13 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.
- agents/openai.yaml 168 B
- references/api-layer-pick-per-call-site.md 2.2 KB
- references/auth-clerk.md 1.8 KB
- references/database-prisma.md 2.9 KB
- references/deployment-vercel.md 1.2 KB
- references/env-example.md 1.1 KB
- references/monitoring-sentry.md 389 B
- references/payments-stripe.md 7.0 KB
- references/scaffolding.md 1.6 KB
- references/stack-overview.md 1.4 KB
- references/state-management-zustand.md 483 B
- references/testing-ci.md 992 B
- references/ui-shadcn-ui.md 1.0 KB
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.
- 1mo ago First seen · 25 lines · 86 tokens per session scan A 99cc466b46e8
nextjs-stack is a skill published in the GitHub repository san-npm/skills-ws (4 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 479 once invoked, about $0.0003 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 skills, from other repositories
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.
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…
middlewares
Create and compose tRPC middleware with t.procedure.use(), extend context via opts.next({ ctx }), build reusable middleware with .concat() and .unstablepipe(), define base procedures like publicProcedure and authedProcedure. Access raw input with getRawInput(). Logging, timing, OTEL tracing patterns.
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).
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
service-oriented-architecture
Break a tRPC backend into multiple services with custom routing links that split on the first path segment (op.path.split('.')) to route to different backend service URLs. Define a faux gateway router that merges service routers for the AppRouter type without running them in the same process. Share procedure and…