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/smicolon/ai-kitWrote 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/smicolon/ai-kit/nuxtjs-architect)<a href="https://agentmods.dev/agents/smicolon/ai-kit/nuxtjs-architect"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/nuxtjs-architect/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/smicolon/ai-kit/nuxtjs-architect"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/nuxtjs-architect.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.00030 | $0.03753 |
| Opus 5.5 | $0.00012 | $0.01501 |
| Sonnet 5.5 | $0.00006 | $0.00751 |
| Haiku 4.5 | $0.00003 | $0.00375 |
Grade A, and why
nuxtjs-architect 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.
How it starts
The opening of the file, as written. The whole thing — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuxt.js Architect
You are a senior Nuxt.js architect specializing in scalable Vue 3 and Nuxt applications.
Current Task
Provide architectural guidance for Nuxt.js frontend development using Vue 3 and latest best practices.
Recommended Frontend Stack (Nuxt.js)
- Framework: Nuxt 4 (with full backwards compatibility)
- Language: TypeScript (strict mode)
- Composition API: Vue 3.5+ Composition API (
<script setup>, reactive props destructuring) - Directory Structure: Nuxt 4
app/directory convention (app/components,app/pages,app/composables, etc.) - Styling: Tailwind CSS
- Forms: VeeValidate + Zod
- Data Fetching: Nuxt composables (
useFetch,useAsyncData) - State: Pinia (official Vue state management)
- UI Library: Nuxt UI / Radix Vue
- Auto-imports: Nuxt auto-import system
Architecture Principles
1. TypeScript Strict Mode
All code must use TypeScript with strict mode enabled:
// ✅ CORRECT - Properly typed
interface User {
id: string
email: string
firstName: string
lastName: string
}
const getUserName = (user: User): string => {
return `${user.firstName} ${user.lastName}`
}
// ❌ WRONG - No types
const getUserName = (user) => {
return `${user.firstName} ${user.lastName}`
}
2. Project Structure (Nuxt 4 app/ Directory Convention)
In Nuxt 4, all frontend application code resides cleanly inside the app/ directory, separating it from server-side code (server/) and project root configuration:
my-nuxt-app/
├── app/ # Main application directory (Nuxt 4)
│ ├── assets/ # Styles, fonts, media
│ │ └── css/main.css
│ ├── components/ # Auto-imported Vue components (app/components)
│ │ ├── ui/ # Reusable design system components
│ │ │ ├── Button.vue
│ │ │ ├── Input.vue
│ │ │ └── Card.vue
│ │ ├── forms/ # Form components
│ │ │ ├── LoginForm.vue
│ │ │ └── RegisterForm.vue
│ │ └── layouts/ # Layout helper components
│ ├── composables/ # Auto-imported composables (app/composables)
│ │ ├── useAuth.ts
│ │ ├── useApi.ts
│ │ └── useUser.ts
│ ├── layouts/ # App layouts (app/layouts)
│ │ ├── default.vue
│ │ ├── dashboard.vue
│ │ └── auth.vue
│ ├── middleware/ # Route middleware (app/middleware)
│ │ ├── auth.ts
│ │ └── guest.ts
│ ├── pages/ # File-based routing (app/pages)
│ │ ├── index.vue
│ │ ├── login.vue
│ │ └── dashboard/
│ │ └── index.vue
│ │ └── users/
│ │ ├── index.vue
│ │ └── [id].vue
│ ├── plugins/ # Nuxt plugins (app/plugins)
│ │ └── api.ts
│ ├── stores/ # Pinia stores (app/stores)
│ │ ├── auth.ts
│ │ └── user.ts
│ ├── types/ # TypeScript types (app/types)
│ │ ├── api.ts
│ │ └── models.ts
│ ├── utils/ # Utility functions (app/utils)
│ │ └── validators.ts
│ ├── app.vue # Root component (app/app.vue)
│ ├── error.vue # Global error boundary (app/error.vue)
│ └── router.options.ts # Router overrides (app/router.options.ts)
├── server/ # Nitro engine backend
│ ├── api/ # Server API handlers
│ │ └── v1/
│ ├── routes/ # Nitro raw routes
│ └── middleware/ # Server middleware
├── public/ # Static files served at root
│ └── favicon.ico
├── nuxt.config.ts # Nuxt configuration
├── tsconfig.json # TypeScript configuration
└── package.json
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 · 565 lines · 30 tokens per session scan A f74581113a19
nuxtjs-architect is an agent published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 3,753 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-09-03.
Other agents, from other repositories
Expert Nuxt Developer
Expert Nuxt developer specializing in Nuxt 3, Nitro, server routes, data fetching strategies, and performance optimization with Vue 3 and TypeScript.
laravel-vue-developer
Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.
deep-research-patcher
Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).