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-state-managementgit 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-state-management)<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/vue-state-management"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-state-management/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-state-management"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-state-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00183 | $0.02753 |
| Opus 5 | $0.00092 | $0.01376 |
| Sonnet 5 | $0.00037 | $0.00551 |
| Haiku 4.5 | $0.00018 | $0.00275 |
Grade A, and why
vue-state-management 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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue 3 State Management Patterns
Same intuition as react-state-management. Pinia replaces Vuex for Vue 3.
Decision tree
| Data | Tool |
|---|---|
| Local component state (count, isOpen) | ref, reactive |
| Shared between siblings | Lift to common parent + props |
| Composable shared logic | composable returning { refs, actions } |
| App-wide state (current user, theme) | Pinia or provide/inject |
| Complex domain state | Pinia |
| Server data with caching | TanStack Query Vue (@tanstack/vue-query) |
| Form state | vee-validate (see vue-forms) |
| URL-synced state | vue-router useRoute().query + useRouter().push |
ref and reactive (covered in vue-conventions)
For component-local state, prefer ref (works for primitives + objects, no destructure footgun).
Composables for shared logic
// src/composables/useCounter.ts
import { ref, computed } from 'vue';
export function useCounter(initial = 0) {
const count = ref(initial);
const double = computed(() => count.value * 2);
function increment() { count.value++; }
function reset() { count.value = initial; }
return { count, double, increment, reset };
}
Each useCounter() call creates a fresh state — composables don't share state by default. For shared state across components, use Pinia.
Pinia (Vue 3 default)
pnpm add pinia. Setup once in main.ts:
import { createApp } from 'vue';
import { createPinia } from 'pinia';
import App from './App.vue';
const app = createApp(App);
app.use(createPinia());
app.mount('#app');
Setup syntax (preferred for Vue 3)
// src/stores/users.ts
import { defineStore } from 'pinia';
import { ref, computed } from 'vue';
import type { User } from '@/types/user';
export const useUserStore = defineStore('users', () => {
// state
const items = ref<User[]>([]);
const currentUser = ref<User | null>(null);
const loading = ref(false);
// getters (computed)
const count = computed(() => items.value.length);
const isAuthenticated = computed(() => currentUser.value !== null);
// actions
async function fetchUsers() {
loading.value = true;
try {
const res = await fetch('/api/users');
items.value = await res.json();
} finally {
loading.value = false;
}
}
function setCurrentUser(user: User | null) {
currentUser.value = user;
}
return { items, currentUser, loading, count, isAuthenticated, fetchUsers, setCurrentUser };
});
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 · 388 lines · 183 tokens per session scan A 0d95587de476
vue-state-management is a skill published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 8d ago), licensed MIT. It adds 183 tokens to every session and 2,753 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.