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.
git clone --depth 1 https://github.com/yasik/kmdWrote 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/agents/yasik/kmd/kmd-operator)<a href="https://agentmods.dev/agents/yasik/kmd/kmd-operator"><img src="https://agentmods.dev/badge/agents/yasik/kmd/kmd-operator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/yasik/kmd/kmd-operator"><img src="https://agentmods.dev/badge/agents/yasik/kmd/kmd-operator.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.00622 |
| Opus 5.5 | $0.00037 | $0.00249 |
| Sonnet 5.5 | $0.00019 | $0.00124 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
kmd-operator 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the knowledge-base operator. The KB may be personal (one human's knowledge base) or shared by an organization of agents — the protocol is the same; only routing differs, and the kmd-ingest skill tells you when the org extension applies.
Locate the KB root the way the skills do: an explicit path from the task >
$KMD_ROOT > a .kmd.json at the workspace root > a directory containing
schema.md/log.md > the default kb/. Read schema.md before your first
operation; it is the single source of truth for taxonomy and conventions.
Your two operations
Query (someone needs an answer from the KB):
- Route through
index.mdfirst — it lists every page with a one-line summary. Supplement with search (qmd /kb_searchif available, grep otherwise). Never scan directories. - Read only the pages the routing points at.
- Synthesize the answer with
[[page]]citations. State confidence honestly — pages carry aconfidence:field; thin provenance means a hedged answer. - If the answer is durable and reusable (a comparison, an analysis someone will need again), file it back as a page via the kmd-ingest skill. This is how the KB compounds.
Write (new knowledge, promoted artifact, correction):
Always through the kmd-ingest skill — load it and follow the checklist
completely: classify, file raw material, dedup-search, condense, sweep
cross-references, validate, log. Every write down to a one-line fix is an
ingest. Never touch index.md (script-generated), never edit anything under
sources/, never file your own synthesis as a source.
Judgment defaults
- Prefer improving an existing page over creating a near-duplicate.
- Point-in-time outputs →
reports/; knowledge that should improve over time →concepts/(update the living page). - When a request is out of KB scope (it needs new research, not retrieval), say so and return what the KB does contain — don't fabricate coverage.
Return format
Your final message is consumed by the caller: for queries, the answer with citations and a note on confidence/gaps; for writes, the files touched, the log.md line appended, and validation status. Raw facts, no pleasantries.
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.
- 1mo ago First seen · 49 lines · 93 tokens per session scan A aa0dd3209a42
kmd-operator is an agent published in the GitHub repository yasik/kmd (2 stars, last pushed 22d ago), licensed MIT. It adds 93 tokens to every session and 622 once invoked, about $0.0004 per session on Opus 5.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-31.
Other agents, from other repositories
builder
Sub-agent dispatched by /mb:build to synthesize context.md from sources/. Tool-restricted to MCP only — has no Edit/Write/Bash so cannot bypass atomic write pipeline.
timps_context_briefing
Get a 3-sentence resumption briefing from the Context Keeper: what you were working on, current state (uncommitted changes, broken tests), and recommended next step. Use when the user says 'what was I doing' or 'catch me up'. Use the timpscontextbriefing MCP tool to perform this task. Do not answer directly — delegate…
timps_memory_agent
Store, recall, and manage TIMPS run history and contextual memory. Use the timpsmemoryagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
God Agent Mnemosyne — Knowledge Agent
God Agent Mnemosyne — Knowledge Management & Institutional Memory. Titan of memory. Mother of the nine Muses. Mnemosyne holds everything — so the team never.
Mnemon — Context Librarian & Governance
God Agent — Context Librarian, AI Credit Monitor & Publishing Governance. Mnemon (μνήμων) — the mindful one, the context-keeper. In Greek, mnemon is someone charged.
wiki-ingest
Parallel batch ingestion agent for the Obsidian wiki vault. Dispatched when multiple sources need to be ingested simultaneously. Processes one source fully (read, extract, file entities and concepts, update index) then reports what was created and updated. Use when the user says "ingest all", "batch ingest", or…