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/capusqa-runsnpx skills add DanielBirk04/capusqa --skill capusqa-runsgit 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/capusqa-runs)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/capusqa-runs"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/capusqa-runs.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.1 | $0.00089 | $0.01214 |
| Opus 5 | $0.00044 | $0.00607 |
| Sonnet 5 | $0.00018 | $0.00243 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade B, and why
capusqa-runs scanned grade B with 2 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`BASE` = the `capusqa` MCP server URL from `~/.codex/config.toml` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s $BASE/api/status` first — no response ⇒ `capusqa serve` (see `$capusqa-help`). This is a copy
92% identical to runs — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capusqa-runs — watch and control runs (Runs)
The dashboard Runs page, in Codex. It reads and controls the daemon's live state,
so every view matches the dashboard and every action persists. (To launch a
test, that's $capusqa-test; for findings, $capusqa-issues.)
Reaching the daemon
BASE = the capusqa MCP server URL from ~/.codex/config.toml
([mcp_servers.capusqa] url = "http://127.0.0.1:7777/mcp" → BASE =
http://127.0.0.1:7777). GET routes need no auth; POST routes add -H "Authorization: Bearer $CAPUSQA_DASHBOARD_TOKEN" only if that env var is set.
curl -s $BASE/api/status first — no response ⇒ capusqa serve (see $capusqa-help).
List runs — "what's running / show my runs"
curl -s $BASE/api/runs → {runs:[…]}, newest first (id, app, created_at,
status, session counts, finding counts, config). Render a compact table; flag
anything still active or with hot (critical/high) findings. The dashboard shows
each run's status as Active, Completed, Stopped, or Couldn't run
— use the same words.
Drill into a run — "show me run X"
curl -s $BASE/api/runs/<run_id> → {run, personas, sessions, findings, finding_groups, clusters, rules}. Summarize per-session status + persona +
verdict, the findings (severity / type / summary), and progress. The dashboard
labels sessions Running, Starting, Done, Waiting, or Needs
attention — match it. (404 unknown run → list /api/runs, let them pick.)
Live — "what's on screen now / watch it"
curl -s $BASE/api/live → {live:[{session_id, run_id, goal, persona_name, steps_taken, …}]}. Live screenshots stream at $BASE/api/live/<session_id>.png
— point them at the dashboard to watch, or fetch a frame. For one session's full
step trace use the trace_get(session_id) MCP tool.
Steer / stop a live session
- Steer:
curl -s -X POST $BASE/api/sessions/<session_id>/steer -H 'content-type: application/json' -d '{"message":"<note>"}'(authed). The note rides the agent's next tool result (no interruption); recorded as anoperatorstep. 409 → not live. - Stop one session:
curl -s -X POST $BASE/api/sessions/<session_id>/stop(authed). Works on a live session OR a terminal failed (needs-attention) one — either way it becomesstopped, which counts as finished. The run's other sessions keep playing. - Restart a failed session:
curl -s -X POST $BASE/api/sessions/<session_id>/restart(authed). Re-queues a needs-attention session and (re)spawns a player to replay it. 409 → the session isn'tfailed. - Stop a whole run:
curl -s -X POST $BASE/api/runs/<run_id>/stop(authed) → terminates the runner + aborts that run's live sessions + finishes the run.
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.
- 5d ago First seen · 77 lines · 89 tokens per session scan B c4976f0413aa
capusqa-runs is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,214 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). It is 92% identical to runs, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
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.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.