Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add PeterCha90/CAP/plugin install capWrote 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/commands/petercha90/cap/setup)<a href="https://agentmods.dev/commands/petercha90/cap/setup"><img src="https://agentmods.dev/badge/commands/petercha90/cap/setup/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/commands/petercha90/cap/setup"><img src="https://agentmods.dev/badge/commands/petercha90/cap/setup.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.00008 | $0.00192 |
| Opus 5.5 | $0.00003 | $0.00077 |
| Sonnet 5.5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade B, and why
setup scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Read `~/.claude/settings.json` (or `$CLAUDE_CONFIG_DIR/settings.json`) What it actually says
Setup Usage HUD
Instructions
- Read
~/.claude/settings.json(or$CLAUDE_CONFIG_DIR/settings.json) - Check if
statusLine.commandcontainsusage-hud - If not configured:
- Back up existing
statusLineto_statusLine_backup - Set
statusLineto{ "type": "command", "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/usage-hud.mjs" } - Save settings.json
- Back up existing
- Verify OAuth token is accessible (macOS Keychain or credentials file)
- Report status and tell user to restart Claude Code if changes were made
Output
Report:
- ✅ or ❌ statusLine configuration
- ✅ or ❌ OAuth token found
- ✅ or ❌ usage-hud.mjs exists at plugin path
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 · 24 lines · 8 tokens per session scan B f6f8cb85ca78
setup is a command published in the GitHub repository PeterCha90/CAP (10 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 192 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
configure
Configure HUD display options (layout, language, presets, display elements) while preserving advanced manual overrides.
land
Resolve and squash merge one named, currently authorized pull request.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
me-cfd-review
Review thermal-fluid CFD setup, boundary conditions, mesh, wall treatment, convergence, validation, and whether the claims are supported.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.