synthesize

synthesize is a command for coding agents from tacoda/keystone. It costs 14 tokens per session (752 once invoked), scanned A, original, MIT.

A command for moving learning notes from an inbox into the right long-term documentation layers. It separates general principles, technology-specific practices, process rules, and sensors, which are checks that observe code or project conditions.

In plain words
What is it for?
Use it to review learning candidates, choose their documentation destination, write the related corpus and guide files, and propose which parts of the codebase the rules should cover.
Why use it?
It gives useful discoveries a defined place and turns them into both explanatory documentation and practical rules for future work.

Command

Install

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.

agentmods
npx agentmods add commands/tacoda/keystone/synthesize
Clone the repo
git clone --depth 1 https://github.com/tacoda/keystone

Wrote 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.

agentmods badge for synthesize

README.md
[![agentmods](https://agentmods.dev/badge/commands/tacoda/keystone/synthesize.svg)](https://agentmods.dev/commands/tacoda/keystone/synthesize)
Your own site
<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>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 8a3746e4b9ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.charter/commands/synthesize.md · 38 lines

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/:

  1. Read the candidate. Note its proposed-layer and (if present) proposed-globs: frontmatter.
  2. Decide the destination:
    • Universal principle → .charter/corpus/principles/<name>.md and .charter/guides/principles/<name>.md
    • Stack idiom → .charter/corpus/idioms/<stack>/<name>.md and .charter/guides/idioms/<stack>/<name>.md
    • Process rule → .charter/guides/process/<name>.md
    • Sensor → .charter/sensors/<name>.md
  3. Author the corpus and guide pair. Corpus explains the why; guide states the rule.
  4. Propose globs: for the guide. If the candidate carries proposed-globs:, use those as the starting point. Otherwise, infer from the evidence: regional surprise → narrow globs that match the touched region (consult corpus/state/CODEBASE_STATE.md's region map); cross-cutting surprise → no globs:. Always show the proposed globs: to the user as part of the guide-write diff — it is part of the rule, not a side detail.
  5. Choose the rule tier. Default: regular rule. Iron law / golden rule only when deviation is genuinely non-negotiable.
  6. Move the candidate from inbox/ to promoted/ (kept), or rejected/ (with a one-line reason in the moved file).
  7. Regenerate .charter/corpus/state/GLOBS_INDEX.md if any guide was written with globs:. Walk every guide, invert the globs, replace the ## Index table (same procedure as bootstrap step 6).
  8. Regenerate Cursor projections if .cursor/rules/ exists. For each newly promoted guide that declares globs:, write .cursor/rules/keystone-<topic>-<name>.mdc mirroring the guide's globs and pointing at the source guide. For any guide whose globs: changed during this synthesize, rewrite the corresponding .mdc. Delete any .cursor/rules/keystone-*.mdc whose guide no longer exists or no longer declares globs:.

Read the full file on GitHub · 38 lines

Changes

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.

  1. 5d ago First seen · 38 lines · 14 tokens per session scan A 8a3746e4b9ca

Subscribe to this mod's changes

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.