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-readme.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-readme)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/verify-readme"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/verify-readme.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.00660 |
| Opus 5 | $0.00000 | $0.00330 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
verify-readme 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify README.md Accuracy
Audit README.md to ensure it accurately reflects the current state of the codebase and provides working instructions.
Step 1: Read Current README.md
Read and understand all content in README.md.
Step 2: Verify Each Section Against Reality
For each section in README.md:
- Project Description - Does it accurately describe what the code actually does?
- Prerequisites - Are version requirements correct?
node --version 2>/dev/null python --version 2>/dev/null go version 2>/dev/null - Installation Commands - Execute each installation step and verify it works
- Run/Start Commands - Verify the main execution command works
- Configuration - Check that documented config files and environment variables exist
- File Paths - Verify all referenced directories and files exist
Step 3: Test All Code Examples
For every code block in README.md:
- Copy the exact command or code
- Execute it in the project root
- Verify it produces the documented result
- Note any errors or unexpected output
# Example: test documented npm commands
npm install
npm run build
npm test
Step 4: Check for Missing Essentials
Identify critical information not in README.md:
- Environment Variables - Are required env vars documented?
grep -r "process.env\|os.environ\|os.Getenv" --include="*.js" --include="*.ts" --include="*.py" --include="*.go" . 2>/dev/null | head -20 - Dependencies - Are system dependencies (databases, services) mentioned?
- Port Numbers - Are default ports documented?
- Common Errors - Are known setup issues addressed?
Step 5: Check for Outdated Information
Look for:
- References to removed files or deprecated features
- Old version numbers or requirements
- Broken links (both internal and external)
- Commands that fail or have changed
- Screenshots that no longer match the UI
# Check for broken internal links
grep -oE '\[.*\]\((\.?/[^)]+)\)' README.md | grep -oE '\(.*\)' | tr -d '()' | while read path; do
[ ! -e "$path" ] && echo "Broken: $path"
done
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.
- 2d ago First seen · 93 lines · 0 tokens per session scan A 39bbc47ca714
verify-readme 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 660 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.
add-api-railway
Create a new Express API endpoint with full integration.
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…
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.