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-refactor)<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-refactor"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-refactor/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-refactor"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-refactor.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.00014 | $0.00303 |
| Opus 5.5 | $0.00006 | $0.00121 |
| Sonnet 5.5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
cc-refactor 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 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.
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
Invoke both skills before doing anything else:
Skill({ skill: "code-simplifier", args: "$ARGUMENTS" })
Skill({ skill: "subagent-driven-development", args: "$ARGUMENTS" })
code-simplifier defines the refactoring rules to apply. subagent-driven-development governs how to delegate each step to sub-agents — one per change, keeping the main context clean.
Diagnose the target file or module:
Complexity issues found:
- Functions over 30 lines: [list with line numbers]
- Nesting over 3 levels: [list with line numbers]
- Classes with 5+ dependencies: [list]
- Layers that only delegate: [list]
- Misleading names: [list]
Generate a refactor plan: ordered list of changes, one per step.
For each step:
- What changes (exact file:line range)
- Why (complexity signal it resolves)
- Risk (what could break)
Execute one change at a time. After each:
- Run the test suite
- Report: tests passed / failed
- Confirm before the next step
Final report:
- Before: [line count, complexity metrics]
- After: [line count, complexity metrics]
- Test status: [passed / N failed]
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 · 43 lines · 14 tokens per session scan A 1ac0e20778f1
cc-refactor is a command published in the GitHub repository yeisonrestrepo/code-conductor (17 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 303 once invoked, about $0.0001 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
generate-changelog
Generate a changelog from git history, grouping commits by type and version.
report
Generate a project analytics report covering code quality, velocity, and health metrics.
explain
Explain a code file, function, or concept in clear, structured language.
audit-deps
Audit all project dependencies for vulnerabilities, licensing issues, and maintenance status.
build-image
Build a Docker image with best practices for caching, security, and size optimization.
env-setup
Set up environment configuration files from templates with validation.