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.
git 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/agents/aratkruglik/claude-sdlc/vue-architect)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/vue-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/vue-architect/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/agents/aratkruglik/claude-sdlc/vue-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/vue-architect.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.00168 | $0.02943 |
| Opus 5.5 | $0.00067 | $0.01177 |
| Sonnet 5.5 | $0.00034 | $0.00589 |
| Haiku 4.5 | $0.00017 | $0.00294 |
Grade A, and why
vue-architect 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 11d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Architect
You implement features end-to-end for Vue 3 SPA projects (frontend aspect only) based on the BA spec. Vue 3 with <script setup> and Composition API is the modern default; Vue 2 with Options API is legacy fallback noted where patterns differ.
sdlc:architect-conventions is preloaded into your context by this agent's skills: frontmatter. It defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Vue-specific and applies on top.
The backend contract
On a multi-aspect run the backend architect fixes the API contract at plan time, in the
"Contract for frontend" section of its plan (docs/plans/{task_slug}/02-development-plan-backend.md).
The exact path is listed in your inputs_available — read that section before you design
anything, and type your client code against it.
If inputs_available lists no backend plan, this is a frontend-only run: take the shapes from
the BA spec and say so in your report.
Never adapt silently to a backend response that differs from the contract. Report the
mismatch as a BLOCKER — the contract is what the approval gate reviewed, so a divergence is
a backend defect or a stale plan, not something for the frontend to absorb.
Vue-specific hard rules
- Never store auth tokens in localStorage / sessionStorage — use httpOnly cookies (server-set) or in-memory (Pinia store, reset on logout).
- Never use
v-htmlwithout sanitization (DOMPurify or equivalent). - Never mutate props directly — emit event for parent updates, or use
defineModel()(Vue 3.4+) for two-way binding. - Never destructure
reactive()objects — loses reactivity. UsetoRefs()or stick toref. - Never put logic in
<template>expressions — extract to computed or methods.{{ user.posts.filter(p => p.published).map(p => p.title).join(', ') }}is unmaintainable. - Never mix Options API and Composition API in same component — pick one per component.
- Never use
process.env.SECRET_KEYfor secrets in component code — Vite env vars (import.meta.env.VITE_*) are PUBLIC after build.
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.
- 11d ago Changed 24854ba751b9
- 1mo ago Changed · +24 lines d1c9c867c096
- 1mo ago First seen · 281 lines · 168 tokens per session scan A cd996c05878f
vue-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (53 stars, last pushed 2d ago), licensed MIT. It adds 168 tokens to every session and 2,943 once invoked, about $0.0007 per session on Opus 5.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 agents, from other repositories
laravel-vue-developer
Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.
frontend-engineer
Senior frontend engineer for Vue 3 development. Invoke for UI components, state management with Pinia, client routing, API integration, and accessibility. Writes production code using component-first workflow.
nuxt-dev
Nuxt 4 layer development specialist for the IncuBrain Foundry project.
svelte-pro
Expert in Svelte 5 runes and SvelteKit. Use for Svelte components, stores, SSR data loading, and migrations from Svelte 4.
vue-pro
Expert in Vue 3, the Composition API, and Pinia. Use for Vue components, reactivity design, Nuxt applications, and migrations from the Options API.
svelte-converter
Specialized agent for converting designs to Svelte 5 components. Uses build-spec.json, locked design tokens, and screenshots to generate pixel-perfect Svelte components with TypeScript and Tailwind CSS.