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-helpnpx skills add DanielBirk04/capusqa --skill capusqa-helpgit 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-help)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/capusqa-help"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/capusqa-help.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.00088 | $0.01112 |
| Opus 5 | $0.00044 | $0.00556 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade B, and why
capusqa-help 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 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
one `$capusqa-*` skill they need. Route, don't lecture. In Codex these skills are Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **daemon down / connection refused / `curl` fails** → it isn't running: How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capusqa-help — the CapusQA menu
You are the navigator: mirror the dashboard's left nav and send the user to the
one $capusqa-* skill they need. Route, don't lecture. In Codex these skills are
invoked with $capusqa-<name> (or via /skills), and Codex also picks them up
implicitly from the task.
Mental model (one breath, only if they're new)
CapusQA is persona-driven LLM testing for web and macOS apps. The daemon
(capusqa serve) is the single source of truth — every run, session, issue and
screenshot lives in ~/.capusqa. This chat and the dashboard
(http://127.0.0.1:7777/) are two clients of it: anything you do here shows in
the dashboard instantly and persists.
If they already said what they want, name the skill (don't show a menu)
- start/launch a test, "test my app", "find bugs" →
$capusqa-test - "what's running", show/watch runs, a session, steer/stop →
$capusqa-runs - bugs/findings, triage, "what did it find", send to my coding tool →
$capusqa-issues - configure anything (modes, run defaults, handoff/coding tool, findings filter, personas, audiences, logins) →
$capusqa-settings - first-time wiring / "nothing works yet" →
$capusqa-setup - update CapusQA / new version / vision models →
$capusqa-update - permissions, daemon health, clicks do nothing →
$capusqa-doctor - open the dashboard / the web UI →
$capusqa-dashboard
If they have no specific intent, ask once (numbered)
Four dashboard areas, recommended first (Setup, Update and Doctor are also available — they can just say so):
- New test (Home) — configure & start a test →
$capusqa-test - Runs — watch live / past runs →
$capusqa-runs - Issues found — findings & fixes →
$capusqa-issues - Settings — configure CapusQA →
$capusqa-settings
Then tell them the one skill to run (e.g. $capusqa-test) — don't make them guess.
The full map
| Skill | = dashboard | Does |
|---|---|---|
$capusqa-test |
New test (Home) | Configure & start a test (app URL, what-to-test, mode) |
$capusqa-runs |
Runs | Watch live/past runs, sessions, traces; steer/stop |
$capusqa-issues |
Issues found | Findings by severity, mark fixed, re-test, send to your coding agent |
$capusqa-settings |
Settings | Test modes · Run defaults · Handoff mode · Findings · Personas · Audiences · Saved secrets · Role logins · Usage · Your plan |
$capusqa-setup |
— | First-run: permissions, vision models, browser, project prep |
$capusqa-update |
— | Update CapusQA + skills + vision models |
$capusqa-doctor |
Home → System status | Environment health + fixes |
$capusqa-dashboard |
the web UI | Open the dashboard in your browser |
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 · 69 lines · 88 tokens per session scan B 9c88cdc4c58b
capusqa-help is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,112 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (strips warnings and disclaimers, 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
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…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
solopi-ai
通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划，管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁，以及 generation 租约的多设备 CI 执行。.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.