Borrowing it
Nothing to install: this file belongs to Insight-Services-APAC/ingenious. 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/Insight-Services-APAC/ingenious/main/.claude/commands/ai-config/verify-claude-md.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/verify-claude-md)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/verify-claude-md"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/verify-claude-md.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.00431 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
verify-claude-md 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
Verify CLAUDE.md Accuracy
Audit CLAUDE.md to ensure it accurately reflects the current state of the codebase.
Step 1: Read Current CLAUDE.md
Read and understand all instructions currently in CLAUDE.md.
Step 2: Verify Each Section Against Reality
For each section or instruction in CLAUDE.md:
- Repository Context - Verify the description matches actual project purpose and structure
- Package Management - Check if the specified package manager (uv, npm, pip, etc.) is actually used
ls pyproject.toml uv.lock package.json pnpm-lock.yaml yarn.lock 2>/dev/null - Build/Run Commands - Test that documented commands actually work
- File Structure - Verify any documented paths or directories exist
- Dependencies - Check if mentioned tools/libraries are in dependency files
- Configuration - Verify any documented config files exist and match descriptions
Step 3: Scan Codebase for Missing Context
Identify important aspects not documented in CLAUDE.md:
- Entry Points - Main files, scripts, or commands to run the application
- Testing - How to run tests, test frameworks used
- Environment Setup - Required environment variables, .env files
- Key Patterns - Architectural patterns, coding conventions used consistently
- External Services - APIs, databases, or services the code interacts with
Step 4: Check for Outdated Information
Look for:
- References to deleted files or directories
- Deprecated commands or workflows
- Old dependency versions or removed packages
- Obsolete configuration instructions
Step 5: Update CLAUDE.md
Fix any inaccuracies found:
- Remove outdated or incorrect information
- Add missing critical context
- Update commands that have changed
- Correct file paths or directory structures
Step 6: Validate Changes
After updates, verify:
- All documented commands execute successfully
- All referenced paths exist
- Instructions are clear and actionable
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 · 55 lines · 0 tokens per session scan A b3ede5470352
verify-claude-md is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 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-09-04.
Other commands, from other repositories
remote-autopilot-install.v1
Remotely install Stakpak Autopilot on any reachable Linux host over SSH, with optional AWS/GCP/Azure VM discovery or provisioning: /remote-autopilot-install.
requirement-review
A command that has several specialized agents review a requirements document and produce a revised version through a controlled workflow.
review
Review a change against the repository's rule-driven modern C++ contract.
add-charts
Integrate Chart.js or Recharts for data visualization. Create reusable chart components: line, bar, pie, area, scatter. Implement responsive sizing with container-based dimensions. Add interactive tooltips showing detailed data on hover. Create customizable legends with click-to-hide series. Support real-time data…
add-api-railway
Create a new Express API endpoint with full integration.
checklist
Generate a custom checklist for the current feature based on user requirements.