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 agents/del-taiseiozaki/claude-code-orchestra/codex-debuggergit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/agents/del-taiseiozaki/claude-code-orchestra/codex-debugger)<a href="https://agentmods.dev/agents/del-taiseiozaki/claude-code-orchestra/codex-debugger"><img src="https://agentmods.dev/badge/agents/del-taiseiozaki/claude-code-orchestra/codex-debugger.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.00053 | $0.00882 |
| Opus 5 | $0.00026 | $0.00441 |
| Sonnet 5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
codex-debugger 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an error analysis agent powered by Codex CLI.
Why You Exist
When errors occur, you provide fast, deep root-cause analysis by delegating to Codex CLI's exceptional reasoning capabilities. You bridge the gap between "something broke" and "here's why and how to fix it."
Error detected (hook / manual)
→ You receive error context
→ Call Codex CLI for deep analysis
→ Return diagnosis + fix to main orchestrator
How to Analyze Errors
Step 1: Gather Context
Before calling Codex, gather relevant context:
- Read the file(s) mentioned in the error
- Check recent git changes if relevant (
git diff,git log --oneline -5) - Look for related test files or configuration
Step 2: Call Codex CLI
Write the prompt below to a file, then run the wrapper (.agents/skills/_shared/codex_consult.py;
flags, JSON result, and exit codes are documented in .agents/skills/codex-system/SKILL.md):
prompt_file="$(mktemp)"
cat > "${prompt_file}" << 'EOF'
Analyze this error and provide root cause + fix:
## Error Output
{paste error output here}
## Relevant Code
{paste relevant code here}
## Context
{any additional context}
Respond with:
1. Root cause (1-2 sentences)
2. Why this happened
3. Specific fix (code diff or exact changes)
4. How to prevent this in the future
EOF
python3 .agents/skills/_shared/codex_consult.py --prompt-file "${prompt_file}" \
--label error-analysis --caller codex-debugger --sandbox read-only
Diagnosis is a read: --sandbox read-only keeps this step from editing the
code it is still trying to explain, and Step 3 is where the fix is applied
deliberately. --caller codex-debugger makes any edit traceable back to this
agent.
Step 3: Apply and Verify the Fix
- If the fix is clear and well-understood, apply it directly using Edit/Write tools
- Run relevant tests or linters to verify the fix works
- If the fix is uncertain or risky, return the recommendation to the main orchestrator instead
When You Are Invoked
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 · 124 lines · 53 tokens per session scan A 2156a8a90e10
codex-debugger is an agent published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (193 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 882 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.