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 DominikTobureto/awesome-grok-build --skill nextjs-fullstackgit clone --depth 1 https://github.com/DominikTobureto/awesome-grok-buildWrote 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/dominiktobureto/awesome-grok-build/nextjs-fullstack)<a href="https://agentmods.dev/skills/dominiktobureto/awesome-grok-build/nextjs-fullstack"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/nextjs-fullstack/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/dominiktobureto/awesome-grok-build/nextjs-fullstack"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/nextjs-fullstack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00392 |
| Opus 5 | $0.00018 | $0.00196 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
nextjs-fullstack 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 12d 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 Fullstack
Ship Next.js features with correct boundaries between server, client, data, and UI.
Grok Build Mode
- Use Plan Mode for routing, auth, persistence, caching, or data-fetching changes.
- Use subagents for broad changes:
routes: app router structure, layouts, metadata.data: DB queries, server actions, validation.client: components, state, forms, accessibility.tests: unit/e2e/build verification.
- Arena-style comparison: compare server action vs API route vs client-only approaches and choose by security, simplicity, and cache behavior.
Workflow
- Detect Next version, package manager, styling, auth, DB, and test setup.
- Keep server-only code out of client components.
- Validate inputs on the server.
- Respect existing caching/revalidation patterns.
- Add loading/error/empty states.
- Run the narrowest relevant checks:
npm run lintnpm run typechecknpm run build- project tests.
Rules
- Do not leak secrets into
NEXT_PUBLIC_*. - Avoid unnecessary client components.
- Do not mutate data without auth and ownership checks.
- Keep forms progressive and resilient.
- Use existing UI primitives and route conventions.
Example Prompts
Use nextjs-fullstack. Plan a server-action implementation for this feature, including validation, auth, tests, and loading/error UI.
Review this Next.js diff for server/client boundary bugs and cache invalidation issues.
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.
- 12d ago First seen · 52 lines · 37 tokens per session scan A f40e8f822f2d
nextjs-fullstack is a skill published in the GitHub repository DominikTobureto/awesome-grok-build (61 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 392 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-30.
Other skills, from other repositories
nextjs-server-components
Use when deciding Server vs Client Component boundaries in Next.js 16, fetching data directly in components, or streaming with Suspense.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
frontend-engineering
A set of front-end engineering rules focused on React and Next.js, tools for building web interfaces. It covers component structure, state organization, accessibility, performance, design constraints, and delivery checks.
igniteui-wc-choose-components
Identify and select the right Ignite UI Web Components for your app UI, then navigate to official docs, usage examples, and API references.
nextjs
Use when building, reviewing, testing, securing, or optimizing a Next.js App Router app: Server vs Client boundaries, use server actions, route handlers, the v15 vs v16 use cache caching model, metadata/SEO, auth, and Core Web Vitals. NOT framework-agnostic React or a Vite SPA (that is react), and NOT visual/UI design…
react
Use when building or reviewing a client-side React SPA bundled by Vite (React 19.2): components, where state lives, hooks, server data fetching, client routing, re-render and effect bugs. NOT App Router / server components / SSR (that is nextjs); NOT native screens (that is react-native).