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-conventionsgit 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-conventions)<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/vue-conventions"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-conventions/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-conventions"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 171 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.
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.00187 | $0.03377 |
| Opus 5 | $0.00093 | $0.01688 |
| Sonnet 5 | $0.00037 | $0.00675 |
| Haiku 4.5 | $0.00019 | $0.00338 |
Grade A, and why
vue-conventions 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue 3 Conventions
This skill consolidates idioms for Vue 3 SPA projects with <script setup> and the Composition API. Apply alongside js-foundation:typescript-patterns (general TS strictness).
Vue 2 fallback notes are at the end — applied only when project is on "vue": "^2".
Project layout
src/
├── main.ts # createApp + mount
├── App.vue # root SFC
├── router/
│ ├── index.ts # createRouter + routes
│ └── guards.ts # navigation guards
├── views/ # route components (page-level)
│ ├── HomeView.vue
│ └── UsersView.vue
├── components/
│ ├── ui/ # primitives (Button, Input, Modal)
│ └── features/ # feature-specific
│ └── users/
│ ├── UserCard.vue
│ └── UserFilter.vue
├── composables/ # use*.ts
│ ├── useDebounce.ts
│ └── useUsers.ts
├── stores/ # Pinia stores
│ └── users.ts
├── lib/ # framework-agnostic utilities
│ └── http.ts
├── types/
│ └── user.ts
└── assets/
└── styles/
└── global.css
Mirror what exists. Don't restructure as part of feature work.
File naming
| What | Convention |
|---|---|
| SFC file | PascalCase.vue (UserCard.vue) |
| View (route) | *View.vue suffix common (UsersView.vue) — match project |
| Composable | useCamelCase.ts (useDebounce.ts) |
| Pinia store | kebab-case.ts or camelCase.ts (users.ts) |
| Test file | *.spec.ts colocated, OR mirror in tests/ |
Component name in <template>: PascalCase (<UserCard />) OR kebab-case (<user-card />) — both work, Vue handles conversion.
SFC structure
<script setup lang="ts">
// 1. Imports
import { ref, computed, onMounted } from 'vue';
import { useRouter } from 'vue-router';
import type { User } from '@/types/user';
// 2. Props/emits/slots
interface Props {
userId: string;
initialName?: string;
}
const props = withDefaults(defineProps<Props>(), { initialName: '' });
const emit = defineEmits<{
save: [name: string];
cancel: [];
}>();
// 3. Reactive state
const name = ref(props.initialName);
const error = ref<string | null>(null);
// 4. Composables
const router = useRouter();
// 5. Computed
const isValid = computed(() => name.value.length >= 2);
// 6. Methods
function onSave() {
if (!isValid.value) {
error.value = 'Name must be at least 2 characters';
return;
}
emit('save', name.value);
}
// 7. Lifecycle
onMounted(() => {
console.log('UserForm mounted for', props.userId);
});
</script>
<template>
<form @submit.prevent="onSave">
<input v-model="name" placeholder="Name" />
<p v-if="error" role="alert">{{ error }}</p>
<div class="actions">
<button :disabled="!isValid">Save</button>
<button type="button" @click="emit('cancel')">Cancel</button>
</div>
</form>
</template>
<style scoped>
form {
display: flex;
flex-direction: column;
gap: 8px;
}
.actions {
display: flex;
gap: 8px;
}
</style>
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 · 469 lines · 187 tokens per session scan A 150f2fa8b4e3
vue-conventions is a skill published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 8d ago), licensed MIT. It adds 187 tokens to every session and 3,377 once invoked, about $0.0009 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.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.