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.03407 |
| Opus 5.5 | $0.00010 | $0.01363 |
| Sonnet 5.5 | $0.00005 | $0.00681 |
| Haiku 4.5 | $0.00002 | $0.00341 |
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 12d 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 — 223 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
Resolve one verification scope before classifying or scanning changes:
- In
pre-prmode, resolve the PR base (gh pr view --json baseRefName -q .baseRefName) or the repository's verified default branch, and freeze the current HEAD SHA. Resolve the merge-base against the available base ref, then usegit diff --no-textconv --no-ext-diff <merge-base-sha> <head-sha>for content and its--name-onlyform for file lists in every diff-based phase below (metadata-only forms such as--name-onlyand--statrender no content and need no such flags). If the base cannot be resolved, report NOT READY with that missing input; do not silently substitute an empty working-tree diff. For a dirty checkout, either verify the committed head in isolation or explicitly include and identify local changes; do not claim tests of a different tree verify the frozen PR head. - In
pre-commitmode, freeze the complete index tree and its staged diff (git diff --no-textconv --no-ext-diff --cached). Run every applicable phase in an isolated checkout of that complete index tree, including unchanged tracked inputs. Preserve the caller's index and unstaged work when preparing verification. Do not copy unstaged source, configuration, or fixtures into the isolated checkout. Report NOT READY if the staged tree cannot be verified in isolation. Before issuing READY, confirm the caller's index still matches the tested snapshot; otherwise repeat verification or report NOT READY. Inquick/fullmode, use the caller's selected scope, defaulting to tracked staged and unstaged changes (git diff --no-textconv --no-ext-diff HEAD) plus explicitly enumerated untracked files. Record the selected scope and tested tree in the report. An empty selected diff is not evidence that a feature branch is unchanged. - Classify the selected files:
- 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: passive prose only; agent instructions, executable snippets, and configuration embedded in Markdown must be classified by the behavior they drive
- frontend: files under
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.
- 12d ago Changed · +2 lines 88e014a28e5b
- 27d ago Changed · +4 lines c39c71235ded
- 1mo ago Changed fb7f88c41069
- 1mo ago Changed 107c48e9ac11
- 1mo ago Changed ce5a7b087a7b
- 1mo ago Changed · +2 lines 350c3371e701
- 1mo ago First seen · 215 lines · 24 tokens per session scan A 442b14e03b41
ia-verify is a command published in the GitHub repository iliaal/whetstone (35 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 3,407 once invoked, about $0.0001 per session on Opus 5.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
octo-deliver
Delivery phase - Review, validate, and test with multi-AI quality assurance.
pre-merge-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
develop
Implement skill development issues with TDD-governed workflow.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…