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 AratKruglik/claude-sdlc --skill vue-routinggit clone --depth 1 https://github.com/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/vue-routing)<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/vue-routing"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-routing/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/aratkruglik/claude-sdlc/vue-routing"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-routing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 57 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 417 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00148 | $0.02880 |
| Opus 5 | $0.00074 | $0.01440 |
| Sonnet 5 | $0.00030 | $0.00576 |
| Haiku 4.5 | $0.00015 | $0.00288 |
Grade A, and why
vue-routing 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 8d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Router v4 Patterns
The de-facto router for Vue 3. Use whatever the project has installed; don't introduce a new router lib.
Setup
// src/router/index.ts
import { createRouter, createWebHistory } from 'vue-router';
import HomeView from '@/views/HomeView.vue';
const router = createRouter({
history: createWebHistory(),
routes: [
{ path: '/', name: 'home', component: HomeView },
{ path: '/about', name: 'about', component: () => import('@/views/AboutView.vue') }, // lazy
{ path: '/users', name: 'users', component: () => import('@/views/UsersView.vue') },
{ path: '/users/:id', name: 'user-detail', component: () => import('@/views/UserDetailView.vue'), props: true },
{ path: '/:pathMatch(.*)*', name: 'not-found', component: () => import('@/views/NotFoundView.vue') },
],
});
export default router;
// src/main.ts
import { createApp } from 'vue';
import App from './App.vue';
import router from './router';
const app = createApp(App);
app.use(router);
app.mount('#app');
<!-- App.vue -->
<template>
<header>
<RouterLink to="/">Home</RouterLink>
<RouterLink to="/about">About</RouterLink>
</header>
<main>
<RouterView />
</main>
</template>
History modes
createWebHistory()— HTML5 History API (/about,/users/123). Requires server config to fall back toindex.htmlfor unmatched routes.createWebHashHistory()— hash-based (/#/about). No server config needed; less SEO-friendly.createMemoryHistory()— for SSR/testing.
Default to createWebHistory() unless deploying to static host without fallback.
Route definitions
const routes = [
// Static
{ path: '/', name: 'home', component: HomeView },
// Dynamic segment
{ path: '/users/:id', name: 'user', component: UserView, props: true },
// Multiple dynamic segments
{ path: '/posts/:category/:slug', component: PostView },
// Optional segment (Vue Router v4: use route alias or two routes)
{ path: '/users/:id/:tab?', component: UserView }, // ? means optional in v4
// Catch-all
{ path: '/:pathMatch(.*)*', component: NotFoundView },
// Aliases (multiple URLs → one component)
{ path: '/home', component: HomeView, alias: '/' },
// Redirects
{ path: '/old-path', redirect: '/new-path' },
{ path: '/old-user/:id', redirect: (to) => ({ path: '/users/' + to.params.id }) },
];
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.
- 8d ago First seen · 419 lines · 148 tokens per session scan A bc81b6544934
vue-routing is a skill published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 7d ago), licensed MIT. It adds 148 tokens to every session and 2,880 once invoked, about $0.0007 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
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.