A command that compares a proposed feature with the tools already listed in a project's tool registry. It reports possible matches and suggests a category and name when a new tool is needed.

It is for checking feature ideas such as changing many request statuses at once. It can identify similar tools, judge whether they are sufficient, and recommend an approach or new-tool naming.

It helps prevent building a duplicate tool and clarifies whether existing tools can be combined to meet the request.

How sawadari/requirements-mcp-server configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/sawadari/requirements-mcp-server/main/.claude/commands/tool-check.md

Clone the repo

git clone --depth 1 https://github.com/sawadari/requirements-mcp-server

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sawadari/requirements-mcp-server/tool-check/github.svg)](https://agentmods.dev/commands/sawadari/requirements-mcp-server/tool-check)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 405 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00000	$0.00162
Sonnet 5.5	$0.00000	$0.00081
Haiku 4.5	$0.00000	$0.00040

Measured 2mo ago against content hash a38c059e2d7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/tool-check.md · 58 lines

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]

Changes

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.

2mo ago First seen · 58 lines · 0 tokens per session scan A a38c059e2d7f

Subscribe to this mod's changes

tool-check is a command published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 12mo 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.

Building agents

tool-check next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tool-checksawadari/requirements-mcp-server	Command	2	12mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

requirements-mcp-server: Command for Claude Code