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-review.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-review)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-review"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-review.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.00010 | $0.00303 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
keystone-review 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 3d 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
97% identical to review — 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
review
Run the four review sensors on the current diff. Semantic check, post-verify. Read .charter/guides/process/review.md.
Activities
Run the four review sensors. If the agent supports parallel sub-agents (Claude Code, etc.), spawn them concurrently — one sub-agent per sensor, all in a single message — and combine their findings. Agents without sub-agent parallelism run the sensors sequentially.
| Sensor | Doc |
|---|---|
| review-functional | .charter/sensors/review-functional.md |
| review-security | .charter/sensors/review-security.md |
| review-risk | .charter/sensors/review-risk.md |
| review-deployment | .charter/sensors/review-deployment.md |
Also run spec-adherence (.charter/sensors/spec-adherence.md) if a spec was authored — walk acceptance criteria line by line against the diff.
Output
Single combined finding list, grouped by sensor, with severity tags.
Gate
Don't ship until the review findings are addressed (fix, ignore-with-reason, or punt to a follow-up issue).
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.
- 3d ago First seen · 28 lines · 10 tokens per session scan A a5b5398e8226
keystone-review is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to review, 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.