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/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/verify)<a href="https://agentmods.dev/commands/tacoda/keystone/verify"><img src="https://agentmods.dev/badge/commands/tacoda/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/verify"><img src="https://agentmods.dev/badge/commands/tacoda/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.00370 |
| Opus 5.5 | $0.00008 | $0.00148 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- keystone-verify — 100% identical, 4 lines differ
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.
- 2mo ago First seen · 30 lines · 19 tokens per session scan A e3096476a786
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 370 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-08-30.
Other commands, from other repositories
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.