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 agentmods add skills/maplecity1314/vite-browser/vite-browser-core-debugnpx skills add MapleCity1314/vite-browser --skill vite-browser-core-debuggit clone --depth 1 https://github.com/MapleCity1314/vite-browserWrote 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/maplecity1314/vite-browser/vite-browser-core-debug)<a href="https://agentmods.dev/skills/maplecity1314/vite-browser/vite-browser-core-debug"><img src="https://agentmods.dev/badge/skills/maplecity1314/vite-browser/vite-browser-core-debug.svg" alt="Measured on agentmods" 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.00062 | $0.00841 |
| Opus 5 | $0.00031 | $0.00420 |
| Sonnet 5 | $0.00012 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
vite-browser-core-debug 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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-browser-core-debug
Use this skill for first-pass diagnosis only. Escalate quickly if the problem is actually runtime or network driven.
Workflow
- Open app and detect framework.
- Run error-first gate (
errors,logs) ANDvite runtime. - IMMEDIATE ROUTING DECISION:
- If
vite runtimeshows HMR Socket closed/error/unknown → escalate tovite-browser-runtime-diagnostics - If
errorscontains "HMR", "hot", "reload", "import", "resolve", "module", "circular", "websocket" → escalate tovite-browser-runtime-diagnostics - If
networkshows 4xx/5xx/FAIL responses → escalate tovite-browser-network-regression - Otherwise, continue with framework state inspection
- If
- Inspect framework state (
vue/react/svelte tree, plus router/pinia for Vue) only if the issue still looks component-driven. - Validate behavior with
network,screenshot, andeval. - Return findings with command evidence and a minimal fix path.
Escalation rules
Escalate to vite-browser-runtime-diagnostics if any of these are true:
- The issue appeared right after a code edit or hot update.
errorsorlogsmention Vite, HMR, reload, import resolution, or websocket instability.- The page refreshes unexpectedly or falls back to full reload.
Escalate to vite-browser-network-regression if:
- The main symptom is wrong data, empty data, or request failure.
networkshows suspicious 4xx/5xx/FAIL responses.
Command sequence
vite-browser open <url>
vite-browser detect
vite-browser vite runtime
vite-browser errors --mapped --inline-source
vite-browser logs
In v0.3.3+, prefer errors --mapped --inline-source over plain errors during first-pass triage. It captures browser-side runtime failures even when the Vite overlay is absent and now aligns better with live propagation diagnosis for Vue store-driven failures.
Then branch based on routing decision:
- Vue:
vite-browser vue treevite-browser vue tree <id>vite-browser vue pinia [store]vite-browser vue router
- React:
vite-browser react treevite-browser react tree <id>vite-browser react store listvite-browser react store inspect <name>vite-browser react hook healthvite-browser react commits [--limit <n>]
- Svelte:
vite-browser svelte treevite-browser svelte tree <id>
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.
- 5d ago First seen · 95 lines · 62 tokens per session scan A 244e97d71881
vite-browser-core-debug is a skill published in the GitHub repository MapleCity1314/vite-browser (9 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 841 once invoked, about $0.0003 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
ui-toolkit/web
Reference skill for Zoom Video SDK UI Toolkit. Use after routing to a web video workflow when you want prebuilt React UI instead of building a fully custom Video SDK interface.
zoom-meeting-sdk-web-component-view
Zoom Meeting SDK Web - Component View. Embeddable Zoom meeting components with Promise-based API for flexible integration. Ideal for React/Vue/Angular apps and custom layouts. Uses ZoomMtgEmbedded with async/await patterns and embeddable UI containers.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
tanstack-form
Headless, performant, and type-safe form state management for TS/JS, React, Vue, Angular, Solid, Lit, and Svelte.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
web-development
Use when users need to implement, integrate, debug, build, deploy, or validate a Web frontend after the product direction is already clear, especially for React, Vue, Vite, browser flows, or CloudBase Web integration.