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 andresquirogadev/skillsense --skill nuxtgit clone --depth 1 https://github.com/andresquirogadev/skillsenseWrote 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/andresquirogadev/skillsense/nuxt)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/nuxt"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/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/andresquirogadev/skillsense/nuxt"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/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.00000 | $0.00530 |
| Opus 5 | $0.00000 | $0.00265 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 9d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuxt Skill
You are working on a Nuxt 3 project. Apply these conventions.
Project Structure
- Pages live in
pages/— file-based routing is automatic. - Shared components in
components/are auto-imported, no explicit imports needed. - Composables in
composables/and utils inutils/are also auto-imported. - Server routes live in
server/api/andserver/routes/. - Static assets go in
public/; processed assets go inassets/.
Data Fetching
- Use
useFetch('/api/…')oruseAsyncData('key', () => $fetch('…'))in pages/components. - These composables are SSR-aware: they run on server, then hydrate on client without double-fetching.
- Use
$fetchinside server routes and event handlers — never useuseFetchserver-side outside composables. - Use
lazy: trueoption inuseFetchto defer loading and avoid blocking navigation. - Call
refreshNuxtData('key')to manually invalidate cached data.
Server Routes
- Create server endpoints in
server/api/[name].ts— export a defaultdefineEventHandler(async (event) => { … }). - Use
readBody(event)for POST bodies,getQuery(event)for query params,getRouterParam(event, 'id')for route params. - Use
createError({ statusCode: 404, statusMessage: 'Not Found' })for HTTP errors.
State & Composables
- Use
useState('key', () => defaultValue)for SSR-safe shared state. - Create composables that return reactive refs for shared logic across components.
- Use
useRuntimeConfig()to access environment variables — server-only vars under.runtimeConfig, public under.runtimeConfig.public.
Auto-imports & TypeScript
- Run
nuxi prepareto regenerate.nuxt/type declarations after adding new composables or components. - Prefix component names to avoid conflicts:
TheHeader.vue,AppButton.vue. - Types for pages are in
.nuxt/types/; useNuxtPage,NuxtLayout, etc.
nuxt.config.ts
- Configure modules in
modules: []; they auto-register plugins and composables. - Use
runtimeConfigfor environment variables; never hardcode secrets. - Use
routeRulesfor per-route rendering strategies (SSR, SWC, prerender, ISR).
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.
- 9d ago First seen · 44 lines · 0 tokens per session scan A c3601fc8f508
nuxt is a skill published in the GitHub repository andresquirogadev/skillsense (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 530 tokens. 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
ph-frontend
(PH) Use only for an explicitly requested scoped UI change with existing design constraints.
ph-visual-qa
(PH) Use only when the user explicitly requests visual verification and a compatible host can render the UI.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
gsap-frameworks
Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is…
soloncode-skin-skill
A tool that packages a visual theme for SolonCode Web UI as an installable ZIP file. SolonCode is a web-based coding interface, and a skin changes its colors, backgrounds, and overall appearance.
My Skill
Content here.