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/outlinegit clone --depth 1 https://github.com/zach-blumenfeld/knowledge-indexWrote 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/zach-blumenfeld/knowledge-index/outline)<a href="https://agentmods.dev/commands/zach-blumenfeld/knowledge-index/outline"><img src="https://agentmods.dev/badge/commands/zach-blumenfeld/knowledge-index/outline.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.00000 | $0.06104 |
| Opus 5 | $0.00000 | $0.03052 |
| Sonnet 5 | $0.00000 | $0.01221 |
| Haiku 4.5 | $0.00000 | $0.00610 |
Grade A, and why
outline 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.
How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outline format for ki outline
The default output of ki outline is a table-of-contents-style render of the vault's containment hierarchy plus its cross-references. It is intended to be readable by both humans and agents: the eye scans display names on the left, and an agent can pick out URIs from a stable right-most column.
The command was previously
ki tree.ki treeis now a permanent alias forki outline— same flags, same output. The format spec below useski outlinethroughout; replace mentally withki treeif you're reading older transcripts.
This document defines the rendered format. Scope and flag semantics (which profile/vault, the positional <uri>, --profile, --depth, back-compat --at) follow docs/scoping.md and the Scoping section just below; the underlying Cypher (B.12) lives in docs/data-model/retrieval-queries.md.
ki outline writes the rendered format to stdout. To save it to a file, pipe (ki outline > outline.txt) — there is no separate output-format flag.
Scoping
ki outline resolves which profile and vault(s) to render the same way the other read commands do (see docs/scoping.md). The positional <uri> is its render root — outline renders that node and everything under it. (This is outline's analog to ki search --under, but it selects the root to render from, not a filter applied to matches.)
- Local (default) — in a vault, no flags: profile + vault come from the working dir (cwd, or
-C <dir>).ki outline <uri>→ render that vault / folder / document / section subtree.ki outline(no uri) → render the vault you're in.
- Remote (
--profile) — reach a profile you're not standing in:ki outline --profile P→ render all vaults in P (multi-root; see Multi-root below).ki outline --profile P <uri>→ render that subtree (the uri names the vault).
-C <dir>relocates the working dir for resolution;--at <uri>is a back-compat alias for the positional<uri>.
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 · 369 lines · 0 tokens per session scan A 39c28377f522
outline is a command published in the GitHub repository zach-blumenfeld/knowledge-index (7 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,104 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.