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.
git clone --depth 1 https://github.com/mzored/superpowers-cc-to-codexWrote 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/mzored/superpowers-cc-to-codex/doctor)<a href="https://agentmods.dev/commands/mzored/superpowers-cc-to-codex/doctor"><img src="https://agentmods.dev/badge/commands/mzored/superpowers-cc-to-codex/doctor/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/mzored/superpowers-cc-to-codex/doctor"><img src="https://agentmods.dev/badge/commands/mzored/superpowers-cc-to-codex/doctor.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.00019 | $0.00170 |
| Opus 5 | $0.00010 | $0.00085 |
| Sonnet 5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
doctor scanned grade A with 0 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run these checks in order:
npm run doctor
The command must verify:
- Codex is installed and authenticated via
scripts/detect-codex.mjs - The installed Codex CLI satisfies the minimum contract via
scripts/check-codex-cli.mjs gitandnodeare available- The MCP server boots cleanly via
scripts/mcp-server.mjs - Plugin manifests validate cleanly via
claude plugin validate .claude-plugin/plugin.json - The current workspace is suitable for adapter-managed state under
.claude/state/codex/
If validation passes but a resume command still fails, inspect saved sessions with commands/codex-state.md.
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.
- 9d ago First seen · 20 lines · 19 tokens per session scan A 844f19499a9f
doctor is a command published in the GitHub repository mzored/superpowers-cc-to-codex (7 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 170 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
v-status
Render the state of a Compound V orchestrator run — pipeline phase plus a per-job status table — by reading state.json from the run directory. Optional run-id argument; without one, list runs and pick the most recent.
debug
Systematic debugging with hypotheses and evidence gathering.
rescue
Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass.
ccc-debug-session
Start a structured debug session with hypothesis tracking and resolution documentation.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-debug
Help debug ESP32 crashes, hangs, and peripheral issues.