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-settingsnpx skills add DanielBirk04/capusqa --skill capusqa-settingsgit 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-settings)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/capusqa-settings"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/capusqa-settings.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.00107 | $0.01873 |
| Opus 5 | $0.00053 | $0.00937 |
| Sonnet 5 | $0.00021 | $0.00375 |
| Haiku 4.5 | $0.00011 | $0.00187 |
Grade B, and why
capusqa-settings 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.
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.
Bearer $CAPUSQA_DASHBOARD_TOKEN"` **only if** that env var is set. `curl -s This is a copy
92% identical to settings — 25 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capusqa-settings — configure CapusQA (Settings)
The dashboard Settings page, in Codex. Ask what to configure, then drive that tab's daemon endpoints. If the user already named the area (e.g. "add a login"), skip the menu and go straight there.
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 = no auth; POST/DELETE add -H "Authorization: Bearer $CAPUSQA_DASHBOARD_TOKEN" only if that env var is set. curl -s $BASE/api/status first.
Ask what to configure (numbered list)
Codex has no structured question tool — present the dashboard's ten tabs (grouped below) as a NUMBERED list, offer the ones that fit the user's hint, and read their number/word reply:
- Testing — Test modes · Run defaults · Handoff mode · Findings
- People & data — Personas · Audiences · Saved secrets · Role logins
- Platform — Usage · Your plan
Then handle the chosen one:
Test modes
The four built-ins (Auto / User experience / Bug / Production — Production is
"Coming soon", not launchable yet) are fixed; users author custom modes =
the override/pin layer on a base profile's smart defaults. List: curl -s $BASE/api/test_modes. Create: POST $BASE/api/test_modes (authed)
{"name":"…","icon":"C","copy":"…","config":{"base":"auto|ux|bug|production", "agent_count":5,"depth":"low|medium|high|xhigh|max","prompt":"extra tester instructions","focus":["checkout","auth"],"audience":["<audience_id>"], "default_goal":"…"}}. Only base is required; every override is optional — omit
agent_count to let the orchestrator size the run, omit depth to match the
chosen thoroughness. Edit: POST $BASE/api/test_modes/<id>. Restore a builtin:
POST $BASE/api/test_modes/<id>/restore_defaults. Delete a custom one: DELETE $BASE/api/test_modes/<id>. (No user-facing engine/thoroughness on a mode —
thoroughness is the per-launch "How thorough" control.)
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 · 122 lines · 107 tokens per session scan B 157b917a8ac5
capusqa-settings is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 107 tokens to every session and 1,873 once invoked, about $0.0005 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 settings, differing in 25 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…
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.