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 kouroshez/coding-os --skill vue-nuxtgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/vue-nuxt)<a href="https://agentmods.dev/skills/kouroshez/coding-os/vue-nuxt"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/vue-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/kouroshez/coding-os/vue-nuxt"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/vue-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.00090 | $0.00563 |
| Opus 5 | $0.00045 | $0.00282 |
| Sonnet 5 | $0.00018 | $0.00113 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
vue-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 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.
What it actually says
REQUIRED BACKGROUND: You MUST also follow the core frontend-fundamentals and clean-code skills. This skill adds Nuxt-3-specific conventions on top.
vue-nuxt
Routing & layout
- File-based routing only — a page is a file under
pages/; never hand-wire vue-router. Dynamic segments:pages/users/[id].vue. app.vuestays a shell (<NuxtLayout><NuxtPage/></NuxtLayout>); layouts live inlayouts/.
Auto-imports (use them, don't fight them)
Components (components/), composables (composables/) and Vue/Nuxt APIs
auto-import. NO manual import { ref } from 'vue' — the linter treats a
redundant import as noise. Composables are named useThing() and live one
per file.
Data fetching (SSR-safe)
useFetch/useAsyncDatain pages and components — never bare$fetchin setup (double-fetches on hydration).- Bare
$fetchis correct inside event handlers and server routes. - Server-only secrets stay in
server/— anything imported by a page ships to the client.
State
Component-local ref/computed first; cross-page state in Pinia stores
(stores/, useXStore naming) per the state-management skill hierarchy —
no global reactive bags.
Server routes
server/api/<name>.<method>.ts exporting defineEventHandler. Validate
input fail-closed; error responses use the shared problem shape
(docs/api-contracts/error-format.md) via createError.
Testing
- Composables: unit tests, pure functions extracted where possible.
- Components: @vue/test-utils with minimal mounting; assert behavior, not markup details.
- Server routes: direct handler invocation with a mocked event.
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.
- 5d ago First seen · 58 lines · 90 tokens per session scan A 5c33612834b7
vue-nuxt is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 90 tokens to every session and 563 once invoked, about $0.0005 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 skills, from other repositories
micro-frontend-architect
Expert guide for designing Micro-Frontend architectures using Webpack Module Federation, Vite Federation, and Single-SPA for large scale Vue and React applications.
vue-frontend-expert
Expert guide for Vue 3 (Composition API), Nuxt 3, and Pinia. Covers advanced reactive state management, syntax, Vue Router, VueUse, and SPA/SSR architectural patterns in English and Indonesian.
web-3d-graphics-expert
Expert guide for WebGL and 3D graphics in the browser using Three.js, Babylon.js, React Three Fiber (R3F), and TresJS. Covers scene optimization, shaders, lighting, 3D model loading (GLTF/GLB), and performance tuning.
svelte-sveltekit-expert
Expert guide for Svelte 5 (Runes) and SvelteKit 2+ — fine-grained reactivity, server-first architecture, form actions, and SSR/SSG / Panduan ahli Svelte 5 (Runes) dan SvelteKit 2+ — reaktivitas fine-grained, arsitektur server-first, form actions, dan SSR/SSG.
component-forge
Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and compound component patterns. Includes scaffold script, reference patterns, and template files for React and Vue. Use when user…
mastermind-component-research
Ground a UI change in the codegraph before writing it — find whether the component already exists, who renders it, and what its props contract is. Use before creating or changing any React or Vue component; triggers "add a component", "change these props", "build this screen", or a Figma frame handed over for…