agentmods.dev

vite-browser-core-debug

vite-browser-core-debug is a skill for Claude Code, Codex from MapleCity1314/vite-browser. It costs 62 tokens per session (841 once invoked), scanned A, original, MIT.

A first-pass debugging workflow for Vue, React, and Svelte applications built with Vite, a tool that serves and updates web apps during development.

In plain words
What is it for?
Use it to inspect framework state, routes, stores, browser errors, logs, network requests, screenshots, and runtime behavior when a Vite page or interface appears broken.
Why use it?
It helps separate component-state bugs from runtime, hot-reload, module-resolution, and network failures before deeper inspection begins.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 9repo 6mo ago A scan 62 tokens original MIT

Good fit Use it to inspect framework state, routes, stores, browser errors, logs, network requests, screenshots, and runtime behavior when a Vite page or interface appears broken.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/maplecity1314/vite-browser/vite-browser-core-debug
View source ↗ MapleCity1314/vite-browser maplecity1314.github.io
Install

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.

Any agent
npx skills add MapleCity1314/vite-browser --skill vite-browser-core-debug
Clone the repo
git clone --depth 1 https://github.com/MapleCity1314/vite-browser

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for vite-browser-core-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/maplecity1314/vite-browser/vite-browser-core-debug/github.svg)](https://agentmods.dev/skills/maplecity1314/vite-browser/vite-browser-core-debug)
Your own site
<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/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.

agentmods 80×15 button for vite-browser-core-debug

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 841 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00841
Opus 5.5 $0.00025 $0.00336
Sonnet 5.5 $0.00012 $0.00168
Haiku 4.5 $0.00006 $0.00084

Measured 1mo ago against content hash 244e97d71881, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/vite-browser-core-debug/SKILL.md · 95 lines

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

  1. Open app and detect framework.
  2. Run error-first gate (errors, logs) AND vite runtime.
  3. IMMEDIATE ROUTING DECISION:
    • If vite runtime shows HMR Socket closed/error/unknown → escalate to vite-browser-runtime-diagnostics
    • If errors contains "HMR", "hot", "reload", "import", "resolve", "module", "circular", "websocket" → escalate to vite-browser-runtime-diagnostics
    • If network shows 4xx/5xx/FAIL responses → escalate to vite-browser-network-regression
    • Otherwise, continue with framework state inspection
  4. Inspect framework state (vue/react/svelte tree, plus router/pinia for Vue) only if the issue still looks component-driven.
  5. Validate behavior with network, screenshot, and eval.
  6. Return findings with command evidence and a minimal fix path.

Escalation rules

Escalate to vite-browser-runtime-diagnostics if any of these are true:

  1. The issue appeared right after a code edit or hot update.
  2. errors or logs mention Vite, HMR, reload, import resolution, or websocket instability.
  3. The page refreshes unexpectedly or falls back to full reload.

Escalate to vite-browser-network-regression if:

  1. The main symptom is wrong data, empty data, or request failure.
  2. network shows 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 tree
    • vite-browser vue tree <id>
    • vite-browser vue pinia [store]
    • vite-browser vue router
  • React:
    • vite-browser react tree
    • vite-browser react tree <id>
    • vite-browser react store list
    • vite-browser react store inspect <name>
    • vite-browser react hook health
    • vite-browser react commits [--limit <n>]
  • Svelte:
    • vite-browser svelte tree
    • vite-browser svelte tree <id>

Read the full file on GitHub · 95 lines

Changes

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.

  1. 1mo ago First seen · 95 lines · 62 tokens per session scan A 244e97d71881

Subscribe to this mod's changes

vite-browser-core-debug is a skill published in the GitHub repository MapleCity1314/vite-browser (9 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 841 once invoked, about $0.0002 per session on Opus 5.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.

DebuggingFrontendReactVue and Svelteai-agentsclidevtoolshmrmodule-graph
Related

Other skills, from other repositories

surf

Drive the user's logged-in Chrome from the shell. Use for browser automation (open, read, click, fill, upload, screenshot), reading a site's feed or API, or asking ChatGPT, Gemini, Perplexity or Grok through the browser.

nicobailon/surf-cli · 53 tokens

devtools-bidirectional

Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.

TanStack/devtools · 59 tokens

devtools-instrumentation

Analyze library codebase for critical architecture and debugging points, add strategic event emissions. Identify middleware boundaries, state transitions, lifecycle hooks. Consolidate events (1 not 15), debounce high-frequency updates, DRY shared payload fields, guard emit() for production. Transparent server/client…

TanStack/devtools · 64 tokens

agent-upkeep

Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…

NVIDIA/elements · 115 tokens

guidance-webgpu-performance

Diagnose and improve browser WebGPU rendering performance, including frame pacing, draw and state-submission overhead, buffer uploads, shaders, and JavaScript work on the render critical path. Use for slow or stuttering GPU-backed interfaces, rendering regressions, CPU/GPU bottleneck analysis, renderer performance…

NVIDIA/elements · 98 tokens

agent-debug-ci

Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…

NVIDIA/elements · 80 tokens