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/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/vue-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/vue-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/vue-expert/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/0xfurai/claude-code-subagents/vue-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/vue-expert.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.00019 | $0.00378 |
| Opus 5.5 | $0.00008 | $0.00151 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
vue-expert 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 1mo 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
Focus Areas
- Vue Composition API and Options API
- Single File Components (SFCs)
- Vue Router for navigation
- Vuex for state management
- Vue directives and custom directives
- Reusable and dynamic components
- Watchers and computed properties
- Lifecycles and hooks
- Props, events, and data binding
- Vue CLI and project scaffolding
Approach
- Use Composition API for code organization
- Modularize code with Single File Components
- Implement Vuex for centralized state management
- Use Vue Router for routing and navigation
- Leverage watchers for reactive behavior
- Utilize computed properties for data derivation
- Apply best practices in component communication
- Manage lifecycles with hooks effectively
- Optimize with lazy loading and code splitting
- Ensure consistency with ESLint and Prettier
Quality Checklist
- Components are modular and reusable
- Code follows Vue style guide
- State is managed with Vuex efficiently
- Proper use of reactive and ref
- Consistent use of computed and methods
- Clear separation of concerns with components
- Lifecycle hooks are correctly implemented
- Routing is properly configured and lazy-loaded
- Proper error handling and fallbacks
- Thorough testing with Vue Test Utils and Jest
Output
- Modern Vue application with clean architecture
- Well-structured directory for scalability
- High-performance front-end with lazy loading
- Consistent codebase with linting setup
- Vuex store with modular approach
- Documentation with JSDoc and comments
- Component library with reusable parts
- Responsive design using CSS frameworks
- Automated testing with high coverage
- Optimized build process for production
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.
- 1mo ago First seen · 57 lines · 19 tokens per session scan A 70b790f88b11
vue-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,019 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 378 once invoked, about $0.0001 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.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
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.
nuxtjs-architect
Senior Nuxt.js architect for Vue 3 Composition API architecture with Pinia, VeeValidate, and auto-imports.
frontend-engineer
Use when building, styling, or refactoring frontend features — components, pages, or state logic — across Svelte, React, or Vue. Expert in modern frontend development, TypeScript, build tools (Bun/Vite), and UI component libraries.