Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-verify)<a href="https://agentmods.dev/commands/iliaal/whetstone/ia-verify"><img src="https://agentmods.dev/badge/commands/iliaal/whetstone/ia-verify/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/iliaal/whetstone/ia-verify"><img src="https://agentmods.dev/badge/commands/iliaal/whetstone/ia-verify.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.00024 | $0.02608 |
| Opus 5 | $0.00012 | $0.01304 |
| Sonnet 5 | $0.00005 | $0.00522 |
| Haiku 4.5 | $0.00002 | $0.00261 |
Grade A, and why
ia-verify 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 yesterday.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Run a structured verification pipeline and produce a single READY / NOT READY report.
Boundary vs /ia-review: /ia-verify is the pre-PR static gate (pass/fail on build/types/lint/tests/security). /ia-review is the multi-agent code review with findings synthesis. Use /ia-verify first to confirm shippable; use /ia-review for design-level assessment.
Mode
$ARGUMENTS -- defaults to full if omitted.
| Mode | What runs |
|---|---|
quick |
Build + type check only |
full |
Build + types + lint + tests |
pre-commit |
Build + types + lint + tests + console.log audit |
pre-pr |
Project-declared gates + build + types + lint + tests + console.log audit + security scan + performance + accessibility + infrastructure + documentation + diff review |
Project-declared gates (phase 0) also run before any push, regardless of mode.
Applicability Detection
Before running the pipeline, classify the change scope from the diff:
-
Run
git diff --name-only(orgit diff --cached --name-onlyfor pre-commit) to get changed files. -
Classify:
- frontend -- files under
src/components/,src/pages/,app/,*.tsx,*.jsx,*.vue,*.svelte,*.css,*.scss, templates - backend -- files under
src/api/,routes/,controllers/,services/,*.php,*.py(non-frontend),*.go, server-side TS - infrastructure -- migration files, Dockerfiles, terraform/ansible, CI configs, env templates, k8s manifests
- docs-only -- only
.md,.txt,CHANGELOG,READMEfiles changed
- frontend -- files under
-
Apply phase filters (pre-pr mode only):
- Performance -- skip for docs-only changes
- Accessibility -- skip for backend-only or docs-only changes
- Infrastructure -- skip for pure frontend changes (no migrations, no env changes, no CI changes)
- Documentation -- always run when user-facing files changed; skip for internal refactors with no API/behavior change
Log which phases were skipped and why in the report.
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.
- yesterday First seen · 215 lines · 24 tokens per session scan A 442b14e03b41
ia-verify is a command published in the GitHub repository iliaal/whetstone (33 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,608 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-09-07.
Other commands, from other repositories
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…
sm-swab
Run slop-mop's iterative development loop for this repository.
responsive
Check that a Divi 5 page works across device sizes (small phones, iPhones, tablets, laptops, widescreen, ultrawide). Uses live viewport testing via a browser MCP server (Chrome DevTools or Playwright) when one is available; falls back to static CSS analysis when not.
f5-gate
Quality gate management with evidence collection.
check
Fast mechanical diagnostics on a section, chapter, part, or full book.
_test-shared
Shared testing patterns and templates (internal).