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/zayne-sprague/dr-claude-code/dashboard-visualizernpx skills add Zayne-sprague/Dr-Claude-Code --skill dashboard-visualizergit clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-CodeWrote 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/zayne-sprague/dr-claude-code/dashboard-visualizer)<a href="https://agentmods.dev/skills/zayne-sprague/dr-claude-code/dashboard-visualizer"><img src="https://agentmods.dev/badge/skills/zayne-sprague/dr-claude-code/dashboard-visualizer.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 | $0.00103 | $0.02225 |
| Opus 5 | $0.00051 | $0.01112 |
| Sonnet 5 | $0.00021 | $0.00445 |
| Haiku 4.5 | $0.00010 | $0.00222 |
Grade A, and why
dashboard-visualizer 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 4d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Visualizer Skill
Project Layout
tools/visualizer/
backend/
app.py # Flask app factory, registers blueprints
api/
experiments.py # /api/experiments/* — experiment metadata, activity logs
manifest.py # /api/manifest/* — HF dataset manifests
model_datasets.py # /api/model/datasets/* — loads HF datasets for model trace viewer
presets.py # /api/presets/* — saved dataset presets
frontend/
src/
App.tsx # Top-level router: routes to Experiments or Visualizer page
hashRouter.ts # Hash-based routing (#page=viz&tab=model)
experiments/ # Experiments page (README, activity log, artifact list)
ExperimentsApp.tsx
api.ts
components/
store.ts
types.ts
model/ # Model Trace Viewer tab
ModelApp.tsx
api.ts
components/
Sidebar.tsx # Dataset selector, preset management
TracePanel.tsx # Side-by-side trace comparison
QuestionNav.tsx # Navigate between questions/examples
InfoBar.tsx # Dataset metadata display
store.ts
types.ts
utils/
visualizer/
VisualizerApp.tsx # Tab bar + router for all visualizer tabs
scripts/
import_experiments.py # Reads notes/experiments/, uploads to HF dashboard dataset
Pages and Tabs
The app has two top-level pages:
1. Experiments Page (#page=experiments)
Shows all experiments in the workspace:
- README content for each experiment
- Activity log (JSONL timeline of steps, go/no-go decisions, notes)
- Artifact list (links to HF datasets)
- Status badges (running, complete, failed, etc.)
Data source: The RESEARCH_DASHBOARD HF dataset, populated by import_experiments.py.
2. Visualizer Page (#page=viz)
A tabbed interface for interactively exploring model output data. Currently has one tab:
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.
- 4d ago First seen · 253 lines · 103 tokens per session scan A 8b48241abd68
dashboard-visualizer is a skill published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 2,225 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…