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/zach-blumenfeld/knowledge-index/theme-formatgit clone --depth 1 https://github.com/zach-blumenfeld/knowledge-indexWhat 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.00000 | $0.02635 |
| Opus 5 | $0.00000 | $0.01318 |
| Sonnet 5 | $0.00000 | $0.00527 |
| Haiku 4.5 | $0.00000 | $0.00264 |
Grade A, and why
theme-format 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Theme format for ki theme
⚠️ Status: DRAFT — not yet implemented.
ki themedoes not exist as a command yet; this is a design doc, not a description of shipping behavior. Format only — how themes are computed (clustering, GDS vs not, ingest vs read time) is out of scope; this pins down what the output looks like in a context window. Companion todocs/commands/outline.md; reuses its row conventions.
Design rule: self-explanatory like outline. No jargon labels that need a guide. Every label is a plain-English phrase that defines its own content, and every count carries its unit inline (in 31 docs, never ×31). A reader (human or agent) seeing the output cold should have no open questions about what a line means.
ki never names a theme (no LLM at ingest/read; #17 rules). Each block carries the evidence an agent needs to name the theme itself, plus full URIs to drill with (ki outline <uri> / ki get <uri>, verbatim round-trip — same contract as outline).
ki theme writes to stdout. Pipe to save; no output-format flag.
Layout
Header
THEMES <vault-name> <N> docs · <G> grouped into <K> themes by wikilinks · <U> ungrouped
by wikilinksis the method statement, in plain words. If the producer degrades (link-sparse vault, capability missing), the phrase changes — e.g.grouped into 6 themes by folders— so differently-derived clusters are never presented identically.<U> ungroupedis always printed, even when 0 — it stops an agent from overclaiming coverage (187 grouped≠ "the vault is about these K things").N = G + Ualways reconciles; the reader can derive coverage % themselves, so none is printed.· <E> excludedis appended only when the run excluded docs (hub pages likeCLAUDE.md/index.mddropped from the whole analysis via--exclude). Excluded docs leave the<N>denominator entirely — the segment exists so that removal is visible, never silent.(showing top <K> — <H> smaller themes cover <D> more docs)is appended when atop_kcut is active. The cut is display-only: the hidden themes remain real (and keep theirthemeIds in the graph) — they are not folded into ungrouped, so<G>still counts them. Crossover lines pointing at hidden themes are suppressed (no danglingT<j>references). Intended first-use pattern: an agent wanting a lay-of-the-land asks for a smalltop_k, reads the header to see how much theme mass is below the cut, and widens only if needed.- Doc counts cover internal md docs only; stubs are excluded.
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.
- 2d ago First seen · 125 lines · 0 tokens per session scan A 3e2266ff5663
theme-format is a command published in the GitHub repository zach-blumenfeld/knowledge-index (6 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,635 tokens. 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-31.
Other commands, from other repositories
performance-review
You goal is to measure and improve performance.
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.