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-updatenpx skills add DanielBirk04/capusqa --skill capusqa-updategit 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-update)<a href="https://agentmods.dev/skills/danielbirk04/capusqa/capusqa-update"><img src="https://agentmods.dev/badge/skills/danielbirk04/capusqa/capusqa-update.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.00079 | $0.00770 |
| Opus 5 | $0.00039 | $0.00385 |
| Sonnet 5 | $0.00016 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade B, and why
capusqa-update 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.
- **Running daemon**: `curl -s $BASE/api/status` → `version`. How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capusqa-update — update CapusQA
CapusQA's setup is install-idempotent, not upgrade-aware: after a new version the
Codex skills and the running daemon can stay on the old one. This skill does the
upgrade end to end. Most of it is shell; only the model refresh goes through the
daemon.
1 — See what you're on
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).
- Running daemon:
curl -s $BASE/api/status→version. - Installed package:
uv tool list | grep capusqa. - Skills:
ls ~/.agents/skills | grep capusqa(the installed Codex skills). If these disagree, that's the upgrade gap — fix below.
2 — Update the package
- From PyPI:
uv tool upgrade capusqa. - From local source (dev):
uv tool install --force '<repo-path>[browser]'([browser]keeps web testing). Confirm withuv tool list | grep capusqa.
3 — Update the Codex skills
The skills are reinstalled from the upgraded package by capusqa setup (which
re-copies them into ~/.agents/skills/); or trigger it directly via POST $BASE/api/setup/install_codex_skills (authed). (Applies in any chat started
after — note that.) Confirm with ls ~/.agents/skills | grep capusqa.
4 — Restart the daemon onto the new version
The running daemon keeps the old code in memory until restarted. Only if no run
is live (curl -s $BASE/api/live shows none):
- Find and stop it:
kill $(lsof -tiTCP:7777 -sTCP:LISTEN). - Start fresh, detached:
capusqa servein a new terminal, ornohup capusqa serve >/tmp/capusqa.log 2>&1 &. Verify:curl -s $BASE/api/statusnow shows the new version.
5 — Vision models (optional)
Refresh OmniParser: curl -s -X POST $BASE/api/models/download (authed), then
poll curl -s $BASE/api/models/status until ready.
6 — Restart Codex
Skills load at the start of a session, so restart Codex or open a new chat to
pick up the new skills. Then /skills and the $capusqa-* set reflect the new
version.
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 · 56 lines · 79 tokens per session scan B a7a17cb162d5
capusqa-update is a skill published in the GitHub repository DanielBirk04/capusqa (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 770 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). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…