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/spec)<a href="https://agentmods.dev/commands/tacoda/keystone/spec"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/spec/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/spec"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/spec.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.00011 | $0.00324 |
| Opus 5.5 | $0.00004 | $0.00130 |
| Sonnet 5.5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- keystone-spec — 97% identical, 4 lines differ
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.
- 1mo ago First seen · 33 lines · 11 tokens per session scan A bd7cf9b9923d
spec is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 324 once invoked, about $0.0000 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.