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/codeweb-dev/spark-ui/verifynpx skills add codeweb-dev/spark-ui --skill verifygit clone --depth 1 https://github.com/codeweb-dev/spark-uiWhat 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 | $0.00020 | $0.00372 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
verify scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Registry endpoints: `curl localhost:3100/r/accordion.json` → 200; excluded slugs (e.g. `/r/slider.json`) → 404 What it actually says
Verifying Spark UI
Build & launch
npm run check # lint + registry:build + production build (all must pass)
PORT=3100 npm run start # serve the production build
Dev alternative: npm run dev (port 3000).
Flows worth driving
/— hero, showcase cards (retained components render), principles, install section, footer/docs/introductionand/docs/components/accordion— sidebar, breadcrumbs, live<ComponentPreview>, npm-first<InstallBlock>- Search: click the navbar search button (⌘K listener lives in the client SearchDialog; button click is more reliable under automation)
- Theme toggle button in navbar (
.darkclass on<html>) - Mobile nav: viewport ≤ 768px,
[aria-label="Open navigation"] - Registry endpoints:
curl localhost:3100/r/accordion.json→ 200; excluded slugs (e.g./r/slider.json) → 404 - CLI install from a scratch project with a minimal
components.json:npx shadcn@latest add http://localhost:3100/r/accordion.json --yes
Gotchas
npm run registry:buildregeneratespublic/r/; run it after touchingregistry.jsonor component sources.- ESLint has 5 accepted warnings (logo-carousel
<img>, number-ticker deps, ghost-ether unused_args); errors must stay at 0. - The public URL comes from
SITE_CONFIG.urlinlib/constants.ts(NEXT_PUBLIC_APP_URLoverride).
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.
- 2d ago First seen · 33 lines · 20 tokens per session scan A 4629acd4e947
verify is a skill published in the GitHub repository codeweb-dev/spark-ui (48 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 372 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
shadcn-vue
Manages shadcn-vue components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-vue, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…
check
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.
health
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…
hunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…
think
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
write
Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like…