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-check-drift.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-check-drift)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-check-drift"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-check-drift.svg" alt="Measured on agentmods" 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.00009 | $0.00386 |
| Opus 5 | $0.00005 | $0.00193 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
keystone-check-drift 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 4d 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
95% identical to check-drift — 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
check-drift
Run the drift sensor on the current diff. Compare the in-progress changes against loaded charter rules. Fast pre-verify check. Read .charter/sensors/drift.md and .charter/guides/process/implementation.md.
Activities
- Identify the diff —
git diff, the staged changes, or the in-progress edits. The list of changed files is the touched-files set for this action. - List which guides apply — load
.charter/guides/idioms/<stack>/*.mdfor each touched stack, plus.charter/guides/process/implementation.mdand any guides from installed policys (.charter/policies/*/guides/). For each candidate, if it declaresglobs:in frontmatter, keep it only when at least one touched file matches; guides withoutglobs:keep today's loading. - Compare diff to guides — line by line, surface violations or hot drift signals. A guide's findings are reported only against files matching its
globs:(or all touched files when noglobs:is set). - Report findings — one bullet per drift. Cite the guide that was violated.
When to invoke
Between implementation and verify. Faster and cheaper than the full verify pass; meant to catch obvious drifts before sensors run.
Index freshness precondition
check-drift reads .keystone/INDEX.json to know which guides apply to the touched files. If the index is stale (any guide file modified more recently than INDEX.json), run keystone index first — otherwise the drift check uses an outdated set of rules.
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.
- 4d ago First seen · 22 lines · 9 tokens per session scan A 95ecb06f06b3
keystone-check-drift is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 386 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to check-drift, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.