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-spec.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-spec)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-spec"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-spec.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.00011 | $0.00315 |
| Opus 5 | $0.00005 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
keystone-spec 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 spec — 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
spec
Capture intent and acceptance criteria for a unit of work. First action on any task. Read .charter/guides/process/spec.md for the full discipline.
Inputs
- A tracker card ID (Jira / Linear / GitHub Issues / Asana), or
- A conversation describing the work, or
- A
TODO.mdentry.
If a tracker card was named, fetch its description via whatever tooling the agent has (MCP server, gh issue view, jira CLI, web fetch). Copy any acceptance criteria into the spec.
Activities
- Restate the intent in your own words.
- List acceptance criteria — explicit, testable bullets a reviewer can verify objectively.
- List non-goals — what is not in scope, to prevent feature creep.
- Flag uncertainty — open questions the user must answer before planning.
- Save the spec to
docs/specs/YYYY-MM-DD-<topic>.mdwith the frontmatter shape described in.charter/guides/process/spec.md(if the project has that location; otherwise capture inline in the chat).
Gate
Do not proceed to planning until the user has explicitly accepted the spec.
Iron law
No proceeding without explicit acceptance criteria. A spec that says "make X better" is not yet a spec.
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 · 31 lines · 11 tokens per session scan A 980aced0028f
keystone-spec is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 315 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 spec, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.