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/signalcompose/claude-tools/cleanupgit 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/cleanup)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/cleanup"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/cleanup.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.00024 | $0.00432 |
| Opus 5 | $0.00012 | $0.00216 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
cleanup 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 3d 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
Step 1: ワークスペースの確認
.x-article/ ディレクトリの内容を一覧表示する。
ls -lh .x-article/ 2>/dev/null || echo ".x-article/ ディレクトリが存在しません"
ディレクトリが存在しない、または空の場合は「クリーンアップ対象のファイルはありません」と報告して終了する。
Step 2: ユーザーへの確認
一覧を表示した後、以下のメッセージでユーザーに確認を求める:
以下のファイルをゴミ箱に移動します:
（ファイル一覧）
よろしいですか？（yes/no）
ユーザーが「no」または「キャンセル」と答えた場合は処理を中止する。
Step 3: ゴミ箱に移動
ユーザーが確認した場合、trash コマンドの有無を確認してから実行する。
trash が利用できない場合は Finder で開く案内を行い、Claude 自身は削除を実行しない。
if command -v trash &>/dev/null; then
trash .x-article/
else
echo "trash コマンドが見つかりません。以下のいずれかを実行してください:"
echo " 1. brew install trash && trash .x-article/"
echo " 2. Finder で手動削除: open .x-article/"
fi
Step 4: 完了報告
.x-article/ をゴミ箱に移動しました。
次回 /x-article:draft を実行すると自動的に再作成されます。
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.
- 3d ago First seen · 50 lines · 24 tokens per session scan A 4e9e68d85c15
cleanup is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 432 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.