Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composernpx agentmods add skills/openaec-foundation/openaec-workspace-composer/vite-errors-buildWrote 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/openaec-foundation/openaec-workspace-composer/vite-errors-build)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/vite-errors-build"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-errors-build/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/openaec-foundation/openaec-workspace-composer/vite-errors-build"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-errors-build.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.00113 | $0.02418 |
| Opus 5 | $0.00056 | $0.01209 |
| Sonnet 5 | $0.00023 | $0.00484 |
| Haiku 4.5 | $0.00011 | $0.00242 |
Grade A, and why
vite-errors-build 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 10d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-errors-build
Quick Reference: Build Error Diagnostic Table
| Symptom | Cause | Fix |
|---|---|---|
Could not resolve './module' |
Unresolved import path | Check file exists, verify resolve.alias config, ensure extensions match resolve.extensions |
Circular dependency detected |
Modules import each other | Refactor shared logic into a third module; use dynamic import() to break the cycle |
[vite]: Rollup failed to resolve import |
Bare import not in node_modules | Run npm install, verify package name spelling, check optimizeDeps.include |
Warning: Some chunks are larger than 500 KiB |
Chunk exceeds build.chunkSizeWarningLimit |
Code-split with dynamic imports, increase limit, or use build.rolldownOptions.output.manualChunks |
build.target: Unexpected token |
Syntax too modern for target browsers | Lower build.target (e.g., 'es2020') or add @vitejs/plugin-legacy |
CSS minification error (v8) |
Lightning CSS cannot parse CSS | Set build.cssMinify: 'esbuild' as fallback; fix invalid CSS syntax |
Sourcemap is likely to be incorrect |
Plugin transforms without sourcemap | Set build.sourcemap: false or fix plugin to emit sourcemaps |
Missing "name" option for UMD export |
Library mode UMD without name |
Add build.lib.name: 'MyLib' for UMD/IIFE formats |
build.rollupOptions is deprecated (v8) |
Using Rollup config key in v8 | Rename to build.rolldownOptions |
BundleError thrown (v8) |
Build API throws structured error | Catch with e.errors array iteration (see v8 Error Handling) |
terser not found |
Terser not installed | Run npm install -D terser; or switch to build.minify: 'oxc' (v8 default) |
esbuild not found (v8) |
esbuild no longer bundled in v8 | Run npm install -D esbuild; or migrate to oxc config |
Could not load content for ... (sourcemap) |
Sourcemap references missing source | Set build.sourcemap: 'hidden' or ensure sources exist |
vite:preloadError in browser |
Dynamic import chunk missing after deploy | Listen for vite:preloadError event, trigger page reload |
emptyOutDir: outDir is not inside root |
Safety check prevents deletion | Pass build.emptyOutDir: true explicitly to override |
assetsDir is ignored in lib mode |
Library mode ignores build.assetsDir |
ALWAYS use flat output or build.rolldownOptions.output.assetFileNames in lib mode |
moduleType not set (v8 plugin) |
Plugin transforms non-JS without declaring type | Add moduleType: 'js' in plugin load/transform hook return |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 227 lines · 113 tokens per session scan A 72b4f2bcc32e
vite-errors-build is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 113 tokens to every session and 2,418 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
aios-exec
A controlled workflow for carrying out clearly defined changes and checks in a project workspace. It covers code, bug fixes, documentation, scripts, tests, linting, type checks, builds, interface changes, and deployment preparation.
aios-arch-health
Deterministic architecture-health governance for repositories. Use when a project needs complexity, duplication, dependency, test, coverage, mutation, QA, performance, database, concurrency, or failure-injection evidence; evidence provenance and artifact digests; protected specification, test, quality-profile, or QA…
threejs-errors-rendering
Use when a Three.js scene renders incorrectly: black screen, invisible objects, wrong colors, z-fighting, or broken shadows. Prevents the common mistake of wrong color space, missing material.side, or forgetting updateProjectionMatrix. Covers all common rendering errors with diagnosis steps and fix patterns. Keywords…
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
devtools
Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include "add devtools", "debug json-render"…
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.