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/yeisonrestrepo/code-conductorWrote 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/yeisonrestrepo/code-conductor/cc-debug)<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-debug"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-debug/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/yeisonrestrepo/code-conductor/cc-debug"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-debug.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.00011 | $0.00360 |
| Opus 5.5 | $0.00004 | $0.00144 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
cc-debug 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 16d 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
Phase 0 — Skill activation
Before doing anything else, invoke both skills in order:
Skill({ skill: "subagent-driven-development", args: "$ARGUMENTS" })
Skill({ skill: "critical-review" })
subagent-driven-development delegates investigation to sub-agents (grep + git log — no inline file reads). critical-review Phase 2 RESILIENCE check then runs on the proposed fix before it is applied — confirm the fix doesn't introduce a silent failure or new boundary condition. The fix must pass Phase 3 self-correction before being committed. End with [VALIDATION].
Characterize the problem before investigating:
Symptom: [what is observed] Expected: [what should happen] Reproduction: [exact steps to reproduce] Frequency: [always / intermittent / only under condition X] Context: [environment, recent changes, logs]
List 2–4 hypotheses ordered by probability. Present them and confirm which to investigate first before touching any code.
For visual bugs or UI flow problems, activate Playwright MCP: "This looks like a visual/UI issue. I'll use Playwright MCP to inspect it — confirm?"
Investigation:
- Use grep to locate relevant code — never read whole files
- Read only the sections that match the hypothesis
- Check git log for recent changes to the area
Report:
- Root cause: [file:line]
- Why it happens: [explanation]
- Impact: [what else could be affected]
- Proposed fix: [exact change]
Apply the fix only after the developer confirms. After fixing, suggest a test that would have caught this bug.
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.
- 16d ago Changed 8de1924f81e6
- 1mo ago First seen · 43 lines · 11 tokens per session scan A 89b04a446c4e
cc-debug is a command published in the GitHub repository yeisonrestrepo/code-conductor (16 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 360 once invoked, about $0.0000 per session on Opus 5.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
check
Drift detector. Diff SPEC.md against code. Read-only, zero writes.
trace
Trace the execution path of a request or operation through the codebase.
debug
Systematically debug an issue by analyzing symptoms, forming hypotheses, and testing them.
env-validate
Validate environment configuration against the template and runtime requirements.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
bisect
Use git bisect to find the exact commit that introduced a bug through binary search.