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.
git clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsnpx agentmods add commands/d-o-hub/github-template-ai-agents/verify-commandsWrote 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/d-o-hub/github-template-ai-agents/verify-commands)<a href="https://agentmods.dev/commands/d-o-hub/github-template-ai-agents/verify-commands"><img src="https://agentmods.dev/badge/commands/d-o-hub/github-template-ai-agents/verify-commands/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.
<a href="https://agentmods.dev/commands/d-o-hub/github-template-ai-agents/verify-commands"><img src="https://agentmods.dev/badge/commands/d-o-hub/github-template-ai-agents/verify-commands.svg" alt="Reviewed on agentmods" width="80" 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.01803 |
| Opus 5.5 | $0.00000 | $0.00721 |
| Sonnet 5.5 | $0.00000 | $0.00361 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade D, and why
verify-commands scanned grade D with 2 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `chmod 777`, `chown -R` Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf`, `del /F /S` How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify-commands
Verify all commands in markdown documentation with intelligent caching.
Description
This command discovers all shell commands in markdown files, validates them using git diff-based cache invalidation, and ensures documentation accuracy with zero token cost after initial setup.
Usage
/scripts/verify-commands.sh [OPTIONS]
Options
| Option | Description |
|---|---|
--force |
Force full validation, bypass cache entirely |
--stats |
Show detailed statistics and cache performance metrics |
--json |
Output results as JSON for programmatic processing |
--quick |
Quick check using cache only (no new validations) |
--silent |
Suppress output except errors |
--help |
Show help message |
Slash Commands
/verify
Quick verification with intelligent caching.
What it does:
- Discovers all commands in markdown files
- Uses git diff-based cache invalidation
- Only revalidates commands affected by recent changes
- Provides cache hit rate statistics
Example output:
📚 PHASE 1: Command Discovery
✓ Found 267 markdown files
✓ Discovered 847 unique commands
🔄 PHASE 2: Cache Check
✓ Cache hit rate: 94.2% (798/847 from cache)
⚡ Validating 49 new/changed commands...
📊 Results:
Safe commands: 623 (73.6%)
Conditional: 178 (21.0%)
Dangerous: 46 (5.4%) - Review required
✅ All commands validated successfully
/verify-force
Force full command verification, bypassing the cache entirely.
What it does:
- Clears the validation cache
- Revalidates ALL commands from scratch
- Establishes fresh baseline
Use when:
- Cache may be corrupted or stale
- After bulk documentation updates
- Debugging cache invalidation issues
- Need to verify validation logic changes
/verify-stats
Show detailed verification statistics and cache performance metrics.
What it provides:
- Cache Performance: Hit rates, last validation commit, cache size
- Command Distribution: Breakdown by category (safe/conditional/dangerous)
- System Availability: Which commands are installed vs unavailable
- Invalidation Analysis: Files changed, commands affected by 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.
- 1mo ago First seen · 314 lines · 0 tokens per session scan D 2511b1efd92f
verify-commands is a command published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,803 tokens. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
generate-widget
Génération Widget Flutter avec Tests.
test-suite
Run comprehensive test suite with coverage analysis.
deps-update
Audit and update dependencies safely.
speckit.companion.living-validate
Check the shape of living specs and a feature spec's deltas — a requirement with no scenario, a scenario missing WHEN or THEN, a duplicate heading, a delta pointing at nothing (opt-in, read-only, never halts).
golden-update
Mise à jour Golden Tests.
ia-test-browser
Run browser tests on pages affected by current PR or branch.