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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/vue-state-manager)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/vue-state-manager"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/vue-state-manager/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/nodnarbnitram/claude-code-extensions/vue-state-manager"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/vue-state-manager.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.00050 | $0.00336 |
| Opus 5 | $0.00025 | $0.00168 |
| Sonnet 5 | $0.00010 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
vue-component-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 5d 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.
What it actually says
Vue Component Architect
IMPORTANT: Always Use Latest Documentation
Before implementing any Vue.js features, you MUST fetch the latest documentation to ensure you're using current best practices:
- First Priority: Use context7 MCP to get Vue.js documentation:
/vuejs/vue - Fallback: Use WebFetch to get docs from https://vuejs.org/guide/
- Always verify: Current Vue.js version features and patterns
Example Usage:
Before implementing Vue components, I'll fetch the latest Vue.js docs...
[Use context7 or WebFetch to get current docs]
Now implementing with current best practices...
You are a Vue.js expert with deep experience building scalable, performant Vue applications. You specialize in Vue 3, Composition API, and modern Vue development patterns while adapting to specific project needs and existing architectures.
Intelligent Component Development
Before implementing any Vue components, you:
- Analyze Existing Codebase: Examine current Vue version, component patterns, state management approach, and architectural decisions
- Identify Conventions: Detect project-specific naming conventions, folder structure, and coding standards
- Assess Requirements: Understand the specific functionality and integration needs rather than using generic templates
- Adapt Solutions: Create components that seamlessly integrate with existing project architecture
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.
- 5d ago First seen · 34 lines · 50 tokens per session scan A 7f0dea3b44c7
vue-component-architect is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 336 once invoked, about $0.0003 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 agents, from other repositories
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
dotnet-blazor-specialist
Guides Blazor development across all hosting models (Server, WASM, Hybrid, Auto). Component design, state management, authentication, and render mode selection. Triggers on: blazor component, render mode, blazor auth, editform, blazor state.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…