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-synthesize.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-synthesize)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-synthesize"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-synthesize.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.00014 | $0.00741 |
| Opus 5 | $0.00007 | $0.00370 |
| Sonnet 5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
keystone-synthesize 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
100% identical to synthesize — 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
synthesize
Promote learning-inbox candidates into the right corpus or guide layer. Read .charter/learning/README.md.
Activities
For each file in .charter/learning/inbox/:
- Read the candidate. Note its
proposed-layerand (if present)proposed-globs:frontmatter. - Decide the destination:
- Universal principle →
.charter/corpus/principles/<name>.mdand.charter/guides/principles/<name>.md - Stack idiom →
.charter/corpus/idioms/<stack>/<name>.mdand.charter/guides/idioms/<stack>/<name>.md - Process rule →
.charter/guides/process/<name>.md - Sensor →
.charter/sensors/<name>.md
- Universal principle →
- Author the corpus and guide pair. Corpus explains the why; guide states the rule.
- Propose
globs:for the guide. If the candidate carriesproposed-globs:, use those as the starting point. Otherwise, infer from the evidence: regional surprise → narrow globs that match the touched region (consultcorpus/state/CODEBASE_STATE.md's region map); cross-cutting surprise → noglobs:. Always show the proposedglobs:to the user as part of the guide-write diff — it is part of the rule, not a side detail. - Choose the rule tier. Default: regular rule. Iron law / golden rule only when deviation is genuinely non-negotiable.
- Move the candidate from
inbox/topromoted/(kept), orrejected/(with a one-line reason in the moved file). - Regenerate
.charter/corpus/state/GLOBS_INDEX.mdif any guide was written withglobs:. Walk every guide, invert the globs, replace the## Indextable (same procedure as bootstrap step 6). - Regenerate Cursor projections if
.cursor/rules/exists. For each newly promoted guide that declaresglobs:, write.cursor/rules/keystone-<topic>-<name>.mdcmirroring the guide's globs and pointing at the source guide. For any guide whoseglobs:changed during this synthesize, rewrite the corresponding.mdc. Delete any.cursor/rules/keystone-*.mdcwhose guide no longer exists or no longer declaresglobs:.
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 · 36 lines · 14 tokens per session scan A 1f6742190325
keystone-synthesize is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 741 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to synthesize, 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.