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 MapleCity1314/vite-browser --skill vite-browser-release-smokegit 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-release-smoke)<a href="https://agentmods.dev/skills/maplecity1314/vite-browser/vite-browser-release-smoke"><img src="https://agentmods.dev/badge/skills/maplecity1314/vite-browser/vite-browser-release-smoke/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/maplecity1314/vite-browser/vite-browser-release-smoke"><img src="https://agentmods.dev/badge/skills/maplecity1314/vite-browser/vite-browser-release-smoke.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.00050 | $0.00621 |
| Opus 5 | $0.00025 | $0.00311 |
| Sonnet 5 | $0.00010 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
vite-browser-release-smoke 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 10d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-browser-release-smoke
Use this skill to produce a consistent go/no-go smoke report.
Scope
Validate:
- App boots and framework detected
- No blocking runtime/build errors
- Core user paths load and navigate
- Network has no critical failures
- HMR/runtime sanity on one edit cycle
- No obvious runtime/diagnosis hit before sign-off
Command template
vite-browser open <url>
vite-browser detect
vite-browser errors --mapped --inline-source
vite-browser logs
vite-browser network
vite-browser vite runtime
vite-browser screenshot
For v0.3.3+, use errors --mapped --inline-source in smoke checks even when no Vite overlay is visible. Browser-side runtime failures should now be treated as release blockers if they surface there or in logs, and live Vue propagation regressions should be checked with both correlate renders and diagnose propagation when store-driven UI failures are in scope.
If Vue app:
vite-browser vue tree
vite-browser vue pinia
vite-browser vue router
Runtime sanity:
vite-browser vite hmr clear
# reproduce one change
vite-browser errors --mapped --inline-source
vite-browser correlate errors --mapped --window 5000
## wait briefly if the repro depends on a UI interaction
vite-browser correlate renders --window 5000
vite-browser diagnose propagation --window 5000
vite-browser diagnose hmr --limit 50
vite-browser vite hmr trace --limit 20
vite-browser vite module-graph clear
vite-browser vite module-graph
vite-browser vite module-graph trace --limit 50
Recovery sanity for v0.3.3+:
# recover the app after one reproduced failure
vite-browser reload
vite-browser errors
The recovered state should return no errors when the page is healthy again. If stale runtime failures persist after recovery, treat that as a release blocker.
Report format
Return:
PASS/FAILby check item- Blocking issues list (if any)
- Diagnosis hits and confidence, if any
- Evidence commands for each failed item
- Final recommendation:
goorno-go
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.
- 10d ago First seen · 89 lines · 50 tokens per session scan A 1b512062f93d
vite-browser-release-smoke is a skill published in the GitHub repository MapleCity1314/vite-browser (9 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 621 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
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
verify-bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
maintain-verification-skill
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.