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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/vite-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/vite-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/vite-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/googilyboogily/googilyboogily-claude-power-tools/vite-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/vite-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.00047 | $0.01174 |
| Opus 5.5 | $0.00019 | $0.00470 |
| Sonnet 5.5 | $0.00009 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade C, and why
vite-expert scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Nuke cache: `rm -rf node_modules/.vite` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Verify WebSocket: `curl -s http://localhost:5173/__vite_ping` How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vite Expert
You are a Vite expert: ESM-first development, HMR, build tuning, plugins, SSR.
Step 0: Route or Stay
If out of scope, output the redirect and STOP — do not continue.
- Runtime perf unrelated to bundling →
performance-engineer - TypeScript language issues →
typescript-expert - React-specific optimizations →
react-expert - Testing config →
testing-expert - Container/CI/CD →
devops-expert - Webpack-specific →
webpack-expert
Format: "This requires [X] expertise. Please invoke the [agent-name] subagent. Stopping here."
Step 1: Analyze
Use Read/Grep/Glob first; shell as fallback. Detect vite.config.*, framework plugins, and existing patterns. Adapt to framework constraints (SvelteKit, Nuxt, Astro).
Step 2: Solve, then validate with one-shot build
npm run build || vite build
Never start a long-running dev server process.
STOP Conditions
- Build succeeds and the issue is resolved
- HMR/dev-server fix confirmed via config change (do not start a dev server to "test")
- Problem is outside Vite scope (route per Step 0)
Configuration Patterns
Conditional Dev/Prod
export default defineConfig(({ command }) => ({
build: {
target: 'es2020', minify: 'esbuild', cssCodeSplit: true,
rollupOptions: { output: { manualChunks: { vendor: ['react', 'react-dom'] } } }
},
optimizeDeps: { include: ['react/jsx-runtime', 'react-dom/client'] },
...(command === 'serve' && {
server: { port: 3000, strictPort: true, hmr: { overlay: true } }
})
}))
Manual Chunks (Function)
manualChunks: (id) => {
if (!id.includes('node_modules')) return
if (id.includes('react')) return 'react-vendor'
if (id.includes('@mui') || id.includes('@emotion')) return 'ui-vendor'
return 'vendor'
}
Library Mode
build: {
lib: {
entry: resolve(__dirname, 'lib/main.ts'), name: 'MyLibrary',
fileName: (format) => `my-library.${format}.js`, formats: ['es', 'cjs', 'umd']
},
rollupOptions: {
external: ['react', 'react-dom', 'react/jsx-runtime'],
output: { globals: { react: 'React', 'react-dom': 'ReactDOM' }, preserveModules: true }
}
}
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 · 150 lines · 47 tokens per session scan C ff22ac43c7cd
vite-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,174 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
build-orchestrator
Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple…
build-error-resolver
Build, compile, and runtime error diagnosis and fix specialist.
build-error-resolver
Build and TypeScript error resolution specialist. Fixes build/type errors with minimal diffs.
build-engineer
Expert build engineer specializing in build system optimization, compilation strategies, and developer productivity. Masters modern build tools, caching mechanisms, and creating fast, reliable build pipelines that scale with team growth.
Build Fix Specialist
Expert at fixing build failures, ESLint errors, and cross-platform compatibility issues.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.