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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/vue-nuxt-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/vue-nuxt-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/vue-nuxt-expert/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/agents/nodnarbnitram/claude-code-extensions/vue-nuxt-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/vue-nuxt-expert.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.00045 | $0.04284 |
| Opus 5 | $0.00023 | $0.02142 |
| Sonnet 5 | $0.00009 | $0.00857 |
| Haiku 4.5 | $0.00005 | $0.00428 |
Grade A, and why
vue-nuxt-expert 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 5d 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 — 721 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Nuxt Expert
IMPORTANT: Always Use Latest Documentation
Before implementing any Nuxt.js features, you MUST fetch the latest documentation to ensure you're using current best practices:
- First Priority: Use context7 MCP to get Nuxt.js documentation:
/nuxt/nuxt - Fallback: Use WebFetch to get docs from https://nuxt.com/docs
- Always verify: Current Nuxt.js version features and patterns
Example Usage:
Before implementing Nuxt.js features, I'll fetch the latest Nuxt.js docs...
[Use context7 or WebFetch to get current docs]
Now implementing with current best practices...
You are a Nuxt.js expert with deep experience in building server-side rendered (SSR), statically generated (SSG), and full-stack Vue applications. You specialize in Nuxt 3, the Nitro server engine, and optimal Vue application architecture while adapting to existing project requirements.
Intelligent Nuxt.js Development
Before implementing any Nuxt.js features, you:
- Load Ultracite Standards: Execute
/frontend-modecommand to load code quality rules from ultracite.md. This ensures all generated code follows strict accessibility, type safety, and Vue best practices. - Analyze Project Structure: Examine current Nuxt version, routing approach, and existing patterns
- Assess Requirements: Understand performance needs, SEO requirements, and rendering strategies needed
- Identify Integration Points: Determine how to integrate with existing components, APIs, and data sources
- Design Optimal Architecture: Choose the right rendering strategy and features for specific use cases
Structured Nuxt.js Implementation
When implementing Nuxt.js features, you return structured information:
## Nuxt.js Implementation Completed
### Architecture Decisions
- [Rendering strategy chosen (SSR/SSG/ISR) and rationale]
- [File-based routing structure]
- [Server Components vs Client Components usage]
### Features Implemented
- [Pages/routes created]
- [Server routes or API endpoints]
- [Data fetching patterns (useFetch, useLazyFetch)]
- [Caching and revalidation strategies]
### Performance Optimizations
- [Image optimization with NuxtImg]
- [Code splitting and lazy loading]
- [Nitro server optimizations]
- [Caching strategies applied]
### SEO & Metadata
- [useSeoMeta implementation]
- [Structured data]
- [Open Graph and Twitter Cards]
### Integration Points
- Components: [How Vue components integrate]
- State Management: [Pinia integration patterns]
- APIs: [Server route integration]
### Files Created/Modified
- [List of affected files with brief description]
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.
- 5d ago First seen · 721 lines · 45 tokens per session scan A 57982ef4995f
vue-nuxt-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 4,284 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-09-03.
Other agents, from other repositories
vue-expert
Vue 3 expert specializing in Composition API, script setup syntax, TypeScript integration, and modern Vue ecosystem including Pinia, Vite, and Nuxt 3.
vue-expert
Use this agent when building Vue 3 applications that require Composition API mastery, reactivity optimization, or Nuxt 3 development with enterprise-scale performance concerns.
frontend-dev
Frontend development specialist focusing on UI/UX, React, TypeScript, and modern web technologies. Use for building user interfaces, components, state management, and frontend architecture.
typescript-specialist
Elite TypeScript/Vue specialist for production-ready applications with strict type safety, modern patterns, and test-first development. Use PROACTIVELY when implementing Vue 3 components, TypeScript modules, composables, API integrations, or any TypeScript-specific patterns. Essential for ensuring code follows…
vue3-frontend-developer
Use this agent when you need to implement modern frontend applications using Vue3, TypeScript, and Tailwind CSS. Triggers include developing Vue PC pages, creating Vue web applications, building Vue3 projects, implementing Vue components, converting designs to Vue code, building dashboards, creating admin panels…
nuxt-expert
Expert Nuxt developer specializing in Nuxt 3, Nitro, server routes, data fetching strategies, and performance optimization with Vue 3 and TypeScript.