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 JakubMikolajek/codex-skills-collection --skill nuxtgit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/jakubmikolajek/codex-skills-collection/nuxt)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/nuxt"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/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/skills/jakubmikolajek/codex-skills-collection/nuxt"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/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.00082 | $0.01063 |
| Opus 5 | $0.00041 | $0.00531 |
| Sonnet 5 | $0.00016 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
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 11d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuxt Implementation Patterns
Use this skill when the task is specifically about Nuxt 3 behavior on top of Vue. Reuse the general vue skill for component discipline and this skill for routing, server boundaries, data loading, composables, and app-level rendering concerns.
Delivery Workflow
Use the checklist below and track progress:
Nuxt progress:
- [ ] Step 1: Discover route, layout, and module conventions
- [ ] Step 2: Map client, server, composable, and runtime-config boundaries
- [ ] Step 3: Implement pages, composables, data loading, and mutations
- [ ] Step 4: Verify middleware, metadata, and error/loading states
- [ ] Step 5: Test route behavior and runtime assumptions
Project Profile Assumptions
- Assume Nuxt 3 by default.
- Assume most routes are client-first or hybrid unless the repository clearly leans on heavy SSR.
- Do not introduce SSR-specific complexity where simple client-side or hybrid rendering matches the current project shape.
- Keep server-side behavior explicit when it is actually required for auth, secrets, protected APIs, or route-level SEO.
Routing and App Structure
- Follow the repository's routing model and file conventions exactly.
- Keep pages, layouts, and shared components clearly separated.
- Treat route params, query params, and server-derived state as explicit inputs.
- Keep framework-specific orchestration in Nuxt layers and push reusable UI into Vue components.
- Prefer composables for reusable route-adjacent logic before introducing broad global state.
Data Fetching and Server Boundaries
- Keep server-only code on the server side.
- Use the project's established data-loading patterns consistently.
- Be explicit about where data is fetched, cached, transformed, and invalidated.
- Model loading, empty, success, and error states intentionally.
- Avoid hiding network behavior deep inside low-level presentational components.
- Prefer the project's existing Nuxt 3 composables and data-loading conventions over ad hoc fetch wrappers.
What ships with it
1 file 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.
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.
- 11d ago First seen · 106 lines · 82 tokens per session scan A 264335615617
nuxt is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,063 once invoked, about $0.0004 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-31.
Other skills, from other repositories
jeecg-codegen
A JeecgBoot code generator that turns a natural-language request into a CRUD module: code for creating, reading, updating, and deleting records. It produces Java backend code, Vue 3 frontend code, menus, permissions, and database migration SQL.
inertia-rails-setup
One-time project initializer for Inertia Rails skills. Detects stack and frontend framework (React/Vue/Svelte) from Gemfile and package.json, offers to install recommended deps (alba-inertia, js-routes, pagy, shadcn), and generates a CLAUDE.md section that configures which skill patterns apply. Use when first…
web-meta-framework-nuxt
Nuxt patterns - file-based routing, data fetching (useFetch/useAsyncData), useState, server routes, middleware, auto-imports, layouts, SEO.
web-meta-framework-sveltekit
SvelteKit full-stack framework - file-based routing, load functions, form actions, server hooks, SSR/SSG, API routes, streaming, progressive enhancement.
framework-expert
Unified framework expertise bundle. Lazy-loads relevant framework patterns (React, Vue, Angular, Next.js, Node.js, Python, Laravel, Go, Flutter, React Native, TypeScript) based on detected tech stack.
nuxt
Skill "nuxt" from ashish7802/awesome-api-skills, covering nuxt skill, ecosystem graph, quick start, production patterns and server api routes.