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-syntax-configgit 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-syntax-config)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-config"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-config/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-syntax-config"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-config.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.00122 | $0.01928 |
| Opus 5 | $0.00061 | $0.00964 |
| Sonnet 5 | $0.00024 | $0.00386 |
| Haiku 4.5 | $0.00012 | $0.00193 |
Grade A, and why
vite-syntax-config 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-syntax-config
Quick Reference
Config File Resolution Order
Vite automatically resolves the config file from the project root in this order:
| File | Format |
|---|---|
vite.config.js |
ES modules or CJS |
vite.config.ts |
TypeScript (transpiled automatically) |
vite.config.mjs |
ES modules (explicit) |
vite.config.mts |
TypeScript ES modules (explicit) |
vite.config.cjs |
CommonJS (explicit) |
vite.config.cts |
TypeScript CommonJS (explicit) |
Shared Options Summary
| Option | Type | Default | Purpose |
|---|---|---|---|
root |
string |
process.cwd() |
Project root (where index.html lives) |
base |
string |
'/' |
Public base path for asset URLs |
mode |
string |
'development' / 'production' |
Environment mode |
define |
Record<string, any> |
-- | Global constant replacements |
plugins |
(Plugin | Plugin[])[] |
[] |
Plugin array (falsy ignored, arrays flattened) |
publicDir |
string | false |
'public' |
Static assets directory |
cacheDir |
string |
'node_modules/.vite' |
Pre-bundling cache location |
logLevel |
'info' | 'warn' | 'error' | 'silent' |
'info' |
Console output verbosity |
customLogger |
Logger |
-- | Custom logger instance |
clearScreen |
boolean |
true |
Clear terminal on server start |
envDir |
string | false |
root |
Directory for .env files |
envPrefix |
string | string[] |
'VITE_' |
Prefix for client-exposed env vars |
appType |
'spa' | 'mpa' | 'custom' |
'spa' |
Application type (controls HTML middleware) |
assetsInclude |
string | RegExp | array |
-- | Additional static asset file types |
future |
Record<string, 'warn' | undefined> |
-- | Opt-in to future breaking changes |
Critical Warnings
NEVER set envPrefix to '' (empty string) -- this exposes ALL environment variables (including DB_PASSWORD, SECRET_KEY, etc.) to client-side code via import.meta.env.
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 · 232 lines · 122 tokens per session scan A d22c1acd8c89
vite-syntax-config is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 122 tokens to every session and 1,928 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.
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.
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.
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.