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/danielbirk04/capusqa/dashboardnpx skills add DanielBirk04/capusqa --skill dashboardgit clone --depth 1 https://github.com/DanielBirk04/capusqaWrote 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/danielbirk04/capusqa/dashboard)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/dashboard"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/dashboard.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.00066 | $0.00342 |
| Opus 5 | $0.00033 | $0.00171 |
| Sonnet 5 | $0.00013 | $0.00068 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
dashboard 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 3d 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.
2. Check the daemon is up: `curl -s $BASE/api/status`. **No response** ⇒ it isn't Copies of this mod
1 near-identical copy found in the catalogue:
- capusqa-dashboard — 88% identical, 17 lines differ
What it actually says
/capusqa:dashboard — open the dashboard in your browser
The dashboard is the daemon's live web UI, a window onto the same store every
/capusqa command writes to. This command just opens it.
Open it
BASE= thecapusqaserver URL in this plugin's.mcp.json(defaulthttp://127.0.0.1:7777; honor a custom--port).- Check the daemon is up:
curl -s $BASE/api/status. No response ⇒ it isn't running — start it withcapusqa serve --open(that serves and opens the dashboard) and you're done. Otherwise continue. - Open it in the default browser:
open "$BASE/"(macOS). - Confirm it's open at
$BASE/, and suggest the user bookmark it (⌘D) so they can find it again — or just run/capusqa:dashboardanytime.
When something's off
Daemon down or open fails → capusqa serve --open in a terminal. On a custom
port the dashboard lives at that port. Anything else → /capusqa:help.
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.
- 3d ago First seen · 24 lines · 66 tokens per session scan A 65b84a6a4df9
dashboard is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 342 once invoked, about $0.0003 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-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…