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/netlify/context-and-toolsWrote 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/rules/netlify/context-and-tools/netlify-frameworks-nuxt)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-frameworks-nuxt"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-frameworks-nuxt/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/rules/netlify/context-and-tools/netlify-frameworks-nuxt"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-frameworks-nuxt.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.00015 | $0.00392 |
| Opus 5.5 | $0.00006 | $0.00157 |
| Sonnet 5.5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
netlify-frameworks-nuxt 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
Nuxt on Netlify
Nuxt 3 is built on Nitro, which has first-class Netlify support. No Netlify adapter or module install is required. When you build on Netlify, Nitro auto-detects the platform and selects its netlify preset, emitting Netlify Functions and Edge Functions for SSR and server routes. You do not add an adapter to nuxt.config the way you would with some other frameworks, and there is no separate Netlify adapter package to install.
Setup
Deploy a standard Nuxt project as-is — Netlify auto-detects Nuxt and configures the build (typically nuxt build). You generally do not need to set the publish directory manually; the Nitro netlify preset writes the static assets and functions where Netlify expects them.
# netlify.toml (optional — Netlify auto-detects Nuxt)
[build]
command = "nuxt build"
Server Routes
Nuxt server routes under server/api/ and server/routes/ are compiled into Netlify Functions by Nitro automatically. Do not hand-author raw Netlify Functions under netlify/functions/ for them.
Environment Variables
Client-exposed values use the NUXT_PUBLIC_ prefix and are read via useRuntimeConfig().public. Server-only values are read via useRuntimeConfig() (private keys) or standard runtime env access. As with any framework, client-exposed values are baked in at build time, so changing them requires a redeploy.
Local Development
npm run dev # nuxt dev
For Netlify platform primitives (Blobs, DB, env vars) during local dev, use netlify dev.
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 · 34 lines · 15 tokens per session scan A 493a41d8f39d
netlify-frameworks-nuxt is a cursor rule published in the GitHub repository netlify/context-and-tools (41 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 392 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-30.
Other cursor rules, from other repositories
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
sveltekit
Writing Svelte code with Go backend and adapter-static using Tailwind CSS, DaisyUI, and Soul AST-generated API endpoints.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
3-vuex@4
APPLY Vuex 4 state management patterns WHEN managing application state to ensure testability, maintainability, and proper separation of concerns in Vue applications.