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/testnpx skills add DanielBirk04/capusqa --skill testgit clone --depth 1 https://github.com/DanielBirk04/capusqaWhat 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.00112 | $0.01953 |
| Opus 5 | $0.00056 | $0.00977 |
| Sonnet 5 | $0.00022 | $0.00391 |
| Haiku 4.5 | $0.00011 | $0.00195 |
Grade A, and why
test 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 yesterday.
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.
`http://127.0.0.1:7777`; honor a custom `--port`). First `curl -s Copies of this mod
1 near-identical copy found in the catalogue:
- capusqa-test — 86% identical, 104 lines differ
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/capusqa:test — configure and start a test (Home)
The dashboard's Home launcher, in chat. Ask what Home asks — every choice as a
multiple-choice AskUserQuestion, in Home's order, using the daemon's exact
wording — then launch through the daemon's HTTP API so it behaves and
persists exactly like clicking Start test on Home. After launch, point the
user at /capusqa:runs (or the dashboard) to watch.
Reaching the daemon
BASE = the capusqa server URL in this plugin's .mcp.json (default
http://127.0.0.1:7777; honor a custom --port). First curl -s $BASE/api/status — no response ⇒ daemon down, tell them capusqa serve (see
/capusqa:help). POST routes here are authed: add -H "Authorization: Bearer $CAPUSQA_DASHBOARD_TOKEN" only if that env var is set (unset by default ⇒ no
header).
A test also needs a runner backend (a Claude Code / Codex CLI, or
OPENAI_API_KEY / ANTHROPIC_API_KEY) — without one the daemon refuses to start
(POST /api/start → 409 {"code":"no_runner_backend"}). curl -s $BASE/api/doctor
and check the runner_backend check; if it's not ok, tell them to install
Claude Code or Codex (or set an API key) and run capusqa setup, then stop —
don't launch.
Pull the launcher options FIRST (so wording matches the dashboard exactly)
curl -s $BASE/api/launcher_options → {modes, thoroughness, policies, defaults} — the SAME source the dashboard Home renders from. Use its strings
verbatim in the questions below (mode name+copy, thoroughness
label+hint, policy title+copy). Never paraphrase; that is the whole point.
(Older daemon 404s? fall back to curl -s $BASE/api/test_modes for the modes
and the built-in quick/standard/deep/exhaustive + report/hot/all lists.)
Gather the config — Home's questions, in order
Infer the free-text fields when you can (target from the cwd repo, a running app,
or a loaded spec; project folder from the cwd) and ask only what's missing.
Everything that is a CHOICE on Home is asked as AskUserQuestion.
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.
- yesterday First seen · 110 lines · 112 tokens per session scan A c200224518ca
test is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 112 tokens to every session and 1,953 once invoked, about $0.0006 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.