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 vuegit 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/vue)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/vue"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/vue/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/vue"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/vue.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.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
vue 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 10d 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.
Vue Skill
You are working on a Vue 3 project. Apply these conventions.
Composition API
- Always use the Composition API with
<script setup>— avoid the Options API for new code. - Declare reactive state with
ref()for primitives andreactive()for objects. - Access
refvalues via.valuein<script setup>; template auto-unwraps them. - Use
computed()for derived values; they are cached automatically. - Use
watch()for side effects on reactive sources; preferwatchEffect()when dependencies are obvious.
Component Design
- Use
defineProps<{ title: string; count?: number }>()for typed props. - Use
defineEmits<{ update: [value: string] }>()for typed events. - Use
defineExpose()only when parent components need to call child methods directly. - Prefer
v-modelover manualemit('update:modelValue')for two-way binding.
Routing (Vue Router 4)
- Define routes in a typed router with
RouteRecordRaw[]. - Use
<RouterLink>for navigation;useRouter()anduseRoute()in<script setup>. - Use route guards with
router.beforeEach()for auth; usemetafields for route metadata. - Lazy-load routes:
() => import('./views/HomeView.vue').
State Management (Pinia)
- Define stores with
defineStore('id', () => { … })(Setup syntax preferred over Options). - Export and use stores only inside components and composables, never in plain JS modules at module scope.
- Use
storeToRefs()to destructure reactive state without losing reactivity.
Reactivity Pitfalls
- Destructuring a
reactive()object breaks reactivity — usetoRefs()first. - Adding new properties to a
reactive()object is fine in Vue 3 (uses Proxy), unlike Vue 2. - Never reassign a
reactive()variable itself; mutate properties instead.
Templates
- Use
v-bind="$attrs"on the root element in components that forward attributes. - Use
:keyonv-foritems that are unique database IDs, not array indices. - Use
v-memoon expensive list items to skip re-renders when data hasn't changed.
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.
- 10d ago First seen · 44 lines · 0 tokens per session scan A d4c205a19863
vue 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 487 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.
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.
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.