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/signalcompose/claude-toolsWrote 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/signalcompose/claude-tools/refactor-team)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/refactor-team"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/refactor-team/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/signalcompose/claude-tools/refactor-team"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/refactor-team.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.00012 | $0.00372 |
| Opus 5.5 | $0.00005 | $0.00149 |
| Sonnet 5.5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
refactor-team 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
Refactor Team
チーム編成によるコードリファクタリング。分析結果をユーザーに提示し、承認後に実行。
使い方
/code:refactor-team [対象パス]
対象パスを省略すると、ベースブランチとの差分ファイルを自動検出します。
ワークフロー
- 対象特定 — 対象ファイルの解決、プロジェクトコンテキスト検出
- リファクタチーム作成 — analyzer + refactorer を起動
- 分析実行 — DRY違反・複雑度・命名・構造を分析、優先度付き提案を作成
- ユーザー承認 — 提案一覧を提示し、実行する項目をユーザーが選択
- リファクタリング実行 — 1リファクタ = 1コミット、テスト通過を確認
- 完了報告 — 実施サマリー表示
制約
- 機能変更は禁止（リファクタリングのみ）
- 各リファクタリングは個別コミット（
refactor:prefix） - ユーザー承認なしの自動実行は禁止
関連
- PRレビュー:
/code:pr-review-team（PR作成後のチームレビュー） - merge 前チェックリスト:
/code:checkup（merge 前に確認したい項目を surface）
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 · 36 lines · 12 tokens per session scan A 0ab2a9ed01ee
refactor-team is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 372 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
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).