Borrowing it
Nothing to install: this file belongs to sawadari/requirements-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sawadari/requirements-mcp-server/main/.claude/commands/tool-check.mdgit clone --depth 1 https://github.com/sawadari/requirements-mcp-serverWrote 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/sawadari/requirements-mcp-server/tool-check)<a href="https://agentmods.dev/commands/sawadari/requirements-mcp-server/tool-check"><img src="https://agentmods.dev/badge/commands/sawadari/requirements-mcp-server/tool-check.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.00000 | $0.00405 |
| Opus 5 | $0.00000 | $0.00202 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
tool-check 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 7d 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
Tool Check Command
新しい機能を実装する前に、既存ツールとの重複をチェックします。
実行内容
config/tool-registry.jsonを読み込み- ユーザーが説明した機能と類似するツールを検索
- 既存ツールで実現可能か判定
- 新規実装が必要な場合、カテゴリとネーミングを提案
使用方法
/tool-check <実装したい機能の説明>
例
/tool-check 要求のステータスを一括変更したい
チェック内容
- 16個の既存ツールとの機能重複
- 関連ツールの組み合わせで実現可能かの判定
- 新規ツール追加が必要な場合の推奨カテゴリ・ネーミング
以下の処理を実行してください：
config/tool-registry.jsonを読み込む- ユーザーの要求を分析
- 既存ツールの中から関連するものを抽出
- 以下の形式で結果を返す：
## 既存ツールの確認結果
### 類似ツール
- **ツール名**: 説明
- **ツール名**: 説明
### 判定
✅ 既存ツールで実現可能 / ❌ 新規ツールが必要
### 推奨アプローチ
1. ...
2. ...
### 新規ツールが必要な場合
- 推奨ツール名: xxx_xxx
- 推奨カテゴリ: crud / analysis / validation / change_management
- 関連ツール: [tool1, tool2]
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.
- 7d ago First seen · 58 lines · 0 tokens per session scan A a38c059e2d7f
tool-check is a command published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 405 tokens. 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.