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.
npx skills add OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill vite-impl-library-modegit clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-ComposerWrote 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-impl-library-mode)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/vite-impl-library-mode"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-impl-library-mode/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-impl-library-mode"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-impl-library-mode.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.00118 | $0.02264 |
| Opus 5 | $0.00059 | $0.01132 |
| Sonnet 5 | $0.00024 | $0.00453 |
| Haiku 4.5 | $0.00012 | $0.00226 |
Grade A, and why
vite-impl-library-mode 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 12d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-impl-library-mode
Quick Reference
build.lib Configuration Options
| Option | Type | Required | Description |
|---|---|---|---|
entry |
string | string[] | Record<string, string> |
YES | Entry point(s) for the library |
name |
string |
UMD/IIFE only | Global variable name exposed on window |
fileName |
string | ((format, entryName) => string) |
NO | Output file name (auto-adds format extension) |
formats |
('es' | 'cjs' | 'umd' | 'iife')[] |
NO | Output formats (see defaults below) |
cssFileName |
string |
NO | Custom CSS output filename |
Default Output Formats
| Entry Type | Default Formats | Reason |
|---|---|---|
| Single entry | ['es', 'umd'] |
UMD provides browser/Node compatibility |
| Multiple entries | ['es', 'cjs'] |
CJS for Node, ES for bundlers |
Critical Warnings
ALWAYS set name when using umd or iife formats -- this defines the global variable name (e.g., window.MyLib). Builds FAIL without it.
ALWAYS externalize peer dependencies (React, Vue, Angular, etc.) -- bundling them causes version conflicts and bloated packages.
NEVER rely on build.assetsDir in library mode -- it has NO effect. Assets are placed alongside output files.
NEVER import CSS at the library entry point and expect consumers to get it automatically -- CSS is extracted to a separate file that consumers MUST import explicitly.
ALWAYS use rolldownOptions.external in Vite 8.x and rollupOptions.external in Vite 6.x/7.x -- the option name changed with the bundler migration.
Decision Tree: Library Mode Setup
Need to build an npm package with Vite?
├── YES → Set build.lib with entry point
│ ├── Single entry point?
│ │ ├── YES → entry: resolve(import.meta.dirname, 'lib/main.ts')
│ │ │ ├── Need browser global (UMD)? → Set name + formats: ['es', 'umd']
│ │ │ └── ESM only? → Set formats: ['es']
│ │ └── NO (multiple entries) → entry: { name: 'path', ... }
│ │ └── Default formats: ['es', 'cjs']
│ ├── Has peer dependencies (React, Vue, etc.)?
│ │ └── YES → Add to rolldownOptions.external + output.globals (UMD)
│ ├── Has CSS?
│ │ └── YES → Set cssFileName, add export to package.json
│ └── Need TypeScript declarations?
│ └── YES → Install vite-plugin-dts
└── NO → Use standard Vite app build
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.
- 12d ago First seen · 335 lines · 118 tokens per session scan A 60dc6f9024c1
vite-impl-library-mode is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 118 tokens to every session and 2,264 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
panel-app-creator
Create or update the Panel UI component of a complete schema v2 NextClaw Mini App or an explicitly loose local Panel. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or for right-side UI, Service Actions, Agent-powered panels, React/Vite panels, and App bridge capability questions.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
color-palette-generator
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.
ui-ux-pro-max
Use when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset and Python search runtime.
panel-app-react-vite-creator
Create or update an engineering-style NextClaw Panel component with pnpm, Vite, React, TypeScript, and Tailwind CSS, then build it into a static .panel directory inside a schema v2 package or an explicitly loose workspace Panel. Use for modern, reusable, complex, Agent-powered, typed Panel interfaces.