Borrowing it
Nothing to install: this file belongs to tacoda/keystone. 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/tacoda/keystone/main/.claude/commands/keystone-verify.mdgit clone --depth 1 https://github.com/tacoda/keystoneWrote 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/tacoda/keystone/keystone-verify)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-verify"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-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/tacoda/keystone/keystone-verify"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-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.00019 | $0.00361 |
| Opus 5.5 | $0.00008 | $0.00144 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
keystone-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 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.
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.
This is a copy
100% identical to verify — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
verify
Run the verification sensors — lint, type-check, test, build, drift, commit-message. Pre-commit gate. Read .charter/guides/process/verification.md.
Activities
Run every sensor classified as runnable in .charter/corpus/state/CODEBASE_STATE.md, in this turn (no stale evidence). For each sensor:
- lint —
.charter/sensors/lint.md. Invoke the project's lint command. - type-check —
.charter/sensors/type-check.md. Invoke the type-check command. Skip if no type checker. - test —
.charter/sensors/test.md. Invoke the test command. Fresh run. - build —
.charter/sensors/build.md. Invoke the build command. - drift —
.charter/sensors/drift.md. Compare diff to loaded guides. - commit-message —
.charter/sensors/commit-message.md. Inspect the proposed message beforegit commit.
Show the actual tool output for each. Do not claim a sensor passed without producing its output this turn.
Iron law
No completion claims without fresh verification evidence. Sensors must run in this turn.
On failure
Return to implementation. Do not "fix forward" inside verify. After the fix, re-invoke verify in a fresh turn.
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 · 28 lines · 19 tokens per session scan A 110203b9bdc1
keystone-verify is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to verify, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
verify
A verification command for FluxDown changes. It runs the checks required by the project, such as formatting, linting changed lines, crate checks, focused tests, image contracts, and CI path checks.
judge-ci-red
Load when: loom-daemon forge wait-checks printed LOOM-CHECKS-RED, or post-verdict.sh … approved exited 6, and a CI-failing verdict is next.
write-test-plan
Generate or update change test plan.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
test-setup
Scaffold test framework and CI pipeline.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…