validate-claude-tools

validate-claude-tools is a command for Claude Code from bacchus-labs/wrangler. It costs 23 tokens per session (3,009 once invoked), scanned A, original, MIT.

A command that checks Claude tools—agents, skills, and related configuration files—against Anthropic's documented rules. It can check one specified path or the whole .claude/ directory.

In plain words
What is it for?
Use it to review Claude configuration and create a CLAUDE_MEMO_AI_TOOLS_REVIEW.md report in the project root.
Why use it?
It helps find invalid settings and frontmatter before Claude tools are used.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is This issue is part of the work defined in: `../specs/SPEC_{name}.md`.

Part of the wrangler plugin — 25 skills, 16 commands, 13 agents shipped together

Good fit Use it to review Claude configuration and create a CLAUDE_MEMO_AI_TOOLS_REVIEW.md report in the project root.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/bacchus-labs/wrangler
agentmods
npx agentmods add commands/bacchus-labs/wrangler/validate-claude-tools

Made for: Claude Code.

Or install wrangler, the plugin that ships this one along with the rest of its 25 skills, 16 commands, 13 agents.

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.

agentmods badge for validate-claude-tools

README.md
[![agentmods](https://agentmods.dev/badge/commands/bacchus-labs/wrangler/validate-claude-tools.svg)](https://agentmods.dev/commands/bacchus-labs/wrangler/validate-claude-tools)
Your own site
<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/validate-claude-tools"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/validate-claude-tools.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,009 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.03009
Opus 5 $0.00012 $0.01504
Sonnet 5 $0.00005 $0.00602
Haiku 4.5 $0.00002 $0.00301

Measured 8d ago against content hash dd30cf11864c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

validate-claude-tools 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 8d 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/validate-claude-tools.md · 371 lines

How it starts

The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Validate Claude AI tools against Anthropic's official documentation and best practices.

Target: $ARGUMENTS (if empty, validate all of .claude/)

Setup

  1. If $ARGUMENTS is provided, validate only that path
  2. If $ARGUMENTS is empty, validate the entire .claude/ directory
  3. Create output file: CLAUDE_MEMO_AI_TOOLS_REVIEW.md in the project root

Frontmatter Schemas

IMPORTANT: Each tool type has different valid frontmatter fields. Use these authoritative schemas.

Subagents (.claude/agents/*.md)

---
name: lowercase-with-hyphens        # Required (max 64 chars)
description: What this agent does   # Required (max 1024 chars)
tools: Read, Write, Bash            # Optional - tools the agent can use
model: sonnet | opus | haiku | inherit  # Optional - defaults to inherit
permissionMode: default | acceptEdits | bypassPermissions | plan | ignore  # Optional
skills: skill1, skill2              # Optional - skills to auto-load
---

Skills (.claude/skills/*/SKILL.md)

---
name: skill-name                    # Required (max 64 chars)
description: What and when          # Required (max 1024 chars)
allowed-tools: ["Read", "Write"]    # Optional - constrain tool access
---

Commands (.claude/commands/*.md)

---
description: What this command does # Required
argument-hint: <arg1> [arg2]        # Optional
allowed-tools: Read, Write          # Optional
model: sonnet | opus | haiku        # Optional - override model for this command
---

Key distinction: Agents use tools: field. Skills and commands use allowed-tools: field. Do not confuse these.


Validation Framework

For each tool type, check the applicable rules below.

Skills (.claude/skills/*/SKILL.md)

Structure validation:

  • SKILL.md exists in skill directory
  • YAML frontmatter has opening and closing --- delimiters
  • Required field: name (lowercase, numbers, hyphens only, max 64 chars)
  • Required field: description (non-empty, max 1024 chars, no XML tags)
  • No reserved words in name: "anthropic", "claude"

Read the full file on GitHub · 371 lines

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.

  1. 8d ago First seen · 371 lines · 23 tokens per session scan A dd30cf11864c

Subscribe to this mod's changes

validate-claude-tools is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 3,009 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.