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 commands/znlnzi/claude-config-studio/refactor-cleangit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/refactor-clean)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/refactor-clean"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/refactor-clean.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.1 | $0.00013 | $0.00276 |
| Opus 5 | $0.00006 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
refactor-clean 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 5d 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
/refactor-clean - 死代码清理
安全地检测和移除未使用的代码。
工作流
1. 检测
运行静态分析工具检测：
- 未使用的导入
- 未调用的函数
- 未引用的变量
- 注释掉的代码块
- 未使用的依赖包
2. 分类
按风险级别分类：
- SAFE: 可安全删除（私有未使用代码）
- CAUTION: 需要确认（公共 API、动态引用）
- DANGER: 高风险（配置、入口文件）
3. 清理
按风险从低到高逐步清理：
- 运行测试 → 确认通过
- 删除 SAFE 类代码
- 运行测试 → 确认通过
- 处理 CAUTION 类（逐个确认）
- 运行测试 → 确认通过
4. 验证
- 完整测试套件通过
- 构建成功
- 无新的 lint 警告
关键规则
在运行测试之前，绝不删除代码！
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.
- 5d ago First seen · 41 lines · 13 tokens per session scan A 91e69983cf16
refactor-clean is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 276 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
type-coverage
Vérification Couverture des Types Python.
debug
Diagnose Ansible playbook issues from symptoms.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
coolify-debug
Diagnose Coolify deployment issues.
error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.