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.
npx agentmods add commands/tacoda/keystone/synthesizegit 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/synthesize)<a href="https://agentmods.dev/commands/tacoda/keystone/synthesize"><img src="https://agentmods.dev/badge/commands/tacoda/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 | $0.00014 | $0.00752 |
| Opus 5 | $0.00007 | $0.00376 |
| Sonnet 5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
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 5d 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-synthesize — 100% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 38 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.
- 5d ago First seen · 38 lines · 14 tokens per session scan A 8a3746e4b9ca
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 752 once invoked, about $0.0001 per session on Opus 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
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
Command "start-10-1" from minicoohei/ai-agent-camp, covering 🎓 lesson 10-1: clasp基本・gasプロジェクト管理, 📍 このセッションでやること, 🎯 準備チェック, 🚀 step 1: claspのインストールと apps script api の確認 and 🚀 step 2: google認証.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.