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-syntax-resolve-cssWrote 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-resolve-css)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-resolve-css"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-resolve-css/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-resolve-css"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-resolve-css.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.00142 | $0.02589 |
| Opus 5 | $0.00071 | $0.01295 |
| Sonnet 5 | $0.00028 | $0.00518 |
| Haiku 4.5 | $0.00014 | $0.00259 |
Grade A, and why
vite-syntax-resolve-css 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 8d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-syntax-resolve-css
Quick Reference — resolve.* Options
| Option | Type | Default | Purpose |
|---|---|---|---|
resolve.alias |
Record<string, string> | Array<{ find, replacement }> |
— | Path aliases for imports |
resolve.dedupe |
string[] |
— | Force single copy of listed deps |
resolve.conditions |
string[] |
['module', 'browser', 'development|production'] |
Conditional exports resolution |
resolve.mainFields |
string[] |
['browser', 'module', 'jsnext:main', 'jsnext'] |
package.json entry fields |
resolve.extensions |
string[] |
['.mjs', '.js', '.mts', '.ts', '.jsx', '.tsx', '.json'] |
Auto-resolved extensions |
resolve.preserveSymlinks |
boolean |
false |
Use original path for identity |
resolve.tsconfigPaths |
boolean |
false |
Enable tsconfig paths resolution |
resolve.conditions — SSR vs Client
| Context | Default Conditions |
|---|---|
| Client | ['module', 'browser', 'development|production'] |
| SSR | ['module', 'node', 'development|production'] |
'development|production' is automatically replaced based on NODE_ENV.
Quick Reference — css.* Options
| Option | Type | Default | Purpose |
|---|---|---|---|
css.modules |
CSSModulesOptions |
— | CSS Modules behavior config |
css.postcss |
string | PostCSSConfig |
— | Inline PostCSS config or config path |
css.preprocessorOptions |
Record<string, object> |
— | Sass/Less/Stylus options |
css.preprocessorMaxWorkers |
number | true |
true (CPUs - 1) |
Max preprocessor threads |
css.devSourcemap |
boolean |
false |
Experimental: dev sourcemaps |
css.transformer |
'postcss' | 'lightningcss' |
'postcss' |
CSS processing engine |
css.lightningcss |
LightningCSSOptions |
— | Lightning CSS config (targets, drafts, etc.) |
Quick Reference — json.* and html.* Options
| Option | Type | Default | Purpose |
|---|---|---|---|
json.namedExports |
boolean |
true |
Named imports from .json files |
json.stringify |
boolean | 'auto' |
'auto' |
Convert to JSON.parse() (>10kB with 'auto') |
html.cspNonce |
string |
— | Nonce placeholder for script/style tags |
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.
- 8d ago First seen · 362 lines · 142 tokens per session scan A 81ef3749b995
vite-syntax-resolve-css is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 142 tokens to every session and 2,589 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
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.
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.
ui-aesthetic
A set of visual design rules for making web pages and components look consistent and readable. It covers icons, colors, typography, spacing, text, accessibility contrast, layout, and restrained animation.
frontend-developer
Becomes a senior frontend developer who builds accessible, performant user interfaces with modern web technologies. Use when the user needs UI components, responsive layouts, accessibility improvements, or frontend performance optimization. Do NOT use when designing backend APIs, configuring server infrastructure, or…
muxy-extension
Best-practice guide for authoring a Muxy extension — how it should look and behave so it reads as a native part of the app. Covers theming (follow the theme, never hardcode colors), the sizing scale, and which surface to use. Mechanics (manifest fields, permissions, the window.muxy API) live in the linked docs.