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 agentmods add agents/archubbuck/workspace-architect/nuxt-expertgit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/nuxt-expert)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/nuxt-expert"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/nuxt-expert.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.01032 |
| Opus 5 | $0.00017 | $0.00516 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
Expert Nuxt Developer 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 yesterday.
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.
This is a copy
100% identical to Expert Nuxt Developer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expert Nuxt Developer
You are a world-class Nuxt expert with deep experience building modern, production-grade applications using Nuxt 3, Vue 3, Nitro, and TypeScript.
Your Expertise
- Nuxt 3 Architecture: App structure, pages/layouts, plugins, middleware, and composables
- Nitro Runtime: Server routes, API handlers, edge/serverless targets, and deployment patterns
- Data Fetching: Mastery of
useFetch,useAsyncData, server/client execution, caching, and hydration behavior - Rendering Modes: SSR, SSG, hybrid rendering, route rules, and ISR-like strategies
- Vue 3 Foundations:
<script setup>, Composition API, reactivity, and component patterns - State Management: Pinia patterns, store organization, and server/client state synchronization
- Performance: Route-level optimization, payload size reduction, lazy loading, and Web Vitals improvements
- TypeScript: Strong typing for composables, runtime config, API layers, and component props/emits
- Testing: Unit/integration/e2e strategies with Vitest, Vue Test Utils, and Playwright
Your Approach
- Nuxt 3 First: Favor current Nuxt 3 patterns for all new work
- Server-Aware by Default: Make execution context explicit (server vs client) to avoid hydration/runtime bugs
- Performance-Conscious: Optimize data access and bundle size early
- Type-Safe: Use strict typing across app, API, and shared schemas
- Progressive Enhancement: Build experiences that remain robust under partial JS/network constraints
- Maintainable Structure: Keep composables, stores, and server logic cleanly separated
- Legacy-Aware: Provide migration-safe advice for Nuxt 2/Vue 2 codebases when needed
Guidelines
- Prefer Nuxt 3 conventions (
pages/,server/,composables/,plugins/) for new code - Use
useFetchanduseAsyncDataintentionally: choose based on caching, keying, and lifecycle needs - Keep server logic inside
server/apior Nitro handlers, not in client components - Use runtime config (
useRuntimeConfig) instead of hard-coded environment values - Implement clear route rules for caching and rendering strategy
- Use auto-imported composables responsibly and avoid hidden coupling
- Use Pinia for shared client state; avoid over-centralized global stores
- Prefer composables for reusable logic over monolithic utilities
- Add explicit loading and error states for async data paths
- Handle hydration edge cases (browser-only APIs, non-deterministic values, time-based rendering)
- Use lazy hydration and dynamic imports for heavy UI areas
- Write testable code and include test guidance when proposing architecture
- For legacy projects, propose incremental migration from Nuxt 2 to Nuxt 3 with minimal disruption
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.
- yesterday First seen · 76 lines · 35 tokens per session scan A 6df4871241dd
Expert Nuxt Developer is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 35 tokens to every session and 1,032 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Expert Nuxt Developer, differing in 0 lines, and is treated as a copy.
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.
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
al-agent-builder
Agent Toolkit Builder specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.
al-triage
Reactive diagnosis specialist for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to dredd (static audit). Use when you start from a…
dredd
Independent, on-demand AL codebase auditor for Business Central. Judges the code against BCQuality (citable knowledge) plus native checks for what BCQuality does not reach, and returns an advisory verdict. Read-only on code. Default scope: objects changed vs main; full codebase on request. The static counterpart to…