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-hmr-apigit 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-hmr-api)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-hmr-api"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-hmr-api/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-hmr-api"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/vite-syntax-hmr-api.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.00157 | $0.02272 |
| Opus 5 | $0.00078 | $0.01136 |
| Sonnet 5 | $0.00031 | $0.00454 |
| Haiku 4.5 | $0.00016 | $0.00227 |
Grade A, and why
vite-syntax-hmr-api 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-syntax-hmr-api
Quick Reference
ViteHotContext — Core Methods
| Method | Purpose | Key Constraint |
|---|---|---|
accept() |
Self-accept hot updates | Whitespace-sensitive static analysis |
accept(dep, cb) |
Accept single dependency update | Path MUST be relative |
accept(deps, cb) |
Accept multiple dependency updates | Array of relative paths |
dispose(cb) |
Cleanup before module replacement | Receives data object for state passing |
prune(cb) |
Cleanup when module removed from graph | Called when no longer imported |
invalidate(message?) |
Force propagation upward | MUST call accept() before invalidate() |
data |
Persistent object across updates | NEVER reassign — ALWAYS mutate properties |
on(event, cb) |
Listen to HMR events | 8 built-in events + custom |
off(event, cb) |
Remove event listener | Must pass same callback reference |
send(event, data?) |
Send custom event to server | Buffered if WebSocket not connected |
Built-in HMR Events
| Event | When Fired |
|---|---|
vite:beforeUpdate |
HMR update is about to be applied |
vite:afterUpdate |
HMR update has been applied |
vite:beforeFullReload |
Full page reload is imminent |
vite:beforePrune |
Modules are about to be pruned |
vite:invalidate |
A module has been invalidated via hot.invalidate() |
vite:error |
An error occurred (e.g., syntax error in updated module) |
vite:ws:disconnect |
WebSocket connection to dev server lost |
vite:ws:connect |
WebSocket connection (re-)established |
Critical Warnings
NEVER use HMR APIs without the guard pattern — production builds MUST tree-shake all HMR code:
if (import.meta.hot) {
// ALL HMR code goes here
}
NEVER add whitespace in import.meta.hot.accept( — Vite uses static analysis that is whitespace-sensitive. Writing import.meta.hot.accept ( or splitting across lines breaks HMR detection.
NEVER reassign import.meta.hot.data — the object reference is shared across updates. ALWAYS mutate properties on it:
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 · 285 lines · 157 tokens per session scan A cc7fb57fd841
vite-syntax-hmr-api is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 157 tokens to every session and 2,272 once invoked, about $0.0008 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
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.