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/mzored/superpowers-cc-to-codex/systematic-debugging-codexnpx skills add mzored/superpowers-cc-to-codex --skill systematic-debugging-codexgit 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/skills/mzored/superpowers-cc-to-codex/systematic-debugging-codex)<a href="https://agentmods.dev/skills/mzored/superpowers-cc-to-codex/systematic-debugging-codex"><img src="https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/systematic-debugging-codex.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.00037 | $0.01239 |
| Opus 5 | $0.00018 | $0.00620 |
| Sonnet 5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
systematic-debugging-codex 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Keep Claude in the main thread for user interaction and fix decisions.
Call codex_debug for bounded root cause investigation (Phases 1-3).
Call codex_implement / codex_resume for applying fixes (Phase 4).
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Checklist
You MUST complete these steps in order:
Phases 1-3: Investigation (Codex)
-
Gather context — collect error messages, stack traces, reproduction steps, recent changes from the user or logs. This is Claude's job.
-
Dispatch investigator — call the
codex_debugMCP tool. Pass a fullpromptbody with the reproduction steps, current evidence, recent changes, and the exact question Codex should answer.
{
"tool": "codex_debug",
"arguments": {
"prompt": "Investigate why Codex-backed agents are still doing repository work locally instead of forwarding through the adapter. Include the current failure mode, relevant files, and the strongest root-cause hypothesis supported by code evidence.",
"workspaceRoot": "/absolute/path/to/your/repo"
}
}
-
Handle the response:
- Success (
resultpopulated): the investigation conforms toschemas/debug-investigation.schema.json(root_cause,evidence,working_examples,hypothesis,suggested_fix). Proceed to validate (Step 4). - Weak or missing evidence: re-dispatch
codex_debugwith a sharper prompt naming the missing pieces (or surface a blocker to the user when needed). - Error (no
result): inspectstderrTailand the resume hint in the error message; resume withcodex_resume(taskId="…")once the cause is resolved.
- Success (
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 118 lines · 37 tokens per session scan A bee4e39e3502
systematic-debugging-codex is a skill published in the GitHub repository mzored/superpowers-cc-to-codex (7 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,239 once invoked, about $0.0002 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 skills, from other repositories
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese specialist role catalogs.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.