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 skills add DanielBirk04/capusqa --skill 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/settings)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/settings"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/settings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/danielbirk04/capusqa/settings"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/settings.svg" alt="Reviewed on agentmods" width="80" 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.00105 | $0.01825 |
| Opus 5.5 | $0.00042 | $0.00730 |
| Sonnet 5.5 | $0.00021 | $0.00365 |
| Haiku 4.5 | $0.00011 | $0.00183 |
Grade A, and why
settings 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 1mo 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.
**only if** that env var is set. `curl -s $BASE/api/status` first. Copies of this mod
1 near-identical copy found in the catalogue:
- capusqa-settings — 92% identical, 25 lines differ
How it starts
The opening of the file, as written. The whole thing — 119 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 chat. 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 URL in .mcp.json (default 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 (AskUserQuestion)
The dashboard groups ten tabs (the picker maxes at 4 options — offer the ones that fit the user's hint, or let them name another):
- 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.)
Run defaults
- Read:
curl -s $BASE/api/settings→.run_defaults+.recovery. Models/effort/backends:curl -s $BASE/api/agent_models. - Save:
POST $BASE/api/settings(authed){"run_defaults":{"model":"", "effort":"","backend":"auto","workers":2,"pacing":"human","scan_depth": "standard","seed":42,"default_credential_ids":[…]},"recovery":{"mode":"ask", "max_retries":2}}. model/effort empty = inherit the backend's default;workersis the Agent limit (max testers per run + concurrent runner workers, 1–16);pacing∈ human|fast;scan_depth∈ quick|standard|deep;recovery.mode∈ ask|auto (the "When a session needs attention" choice).
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.
- 1mo ago First seen · 119 lines · 105 tokens per session scan A 19f7c3410abe
settings is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,825 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…