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 skills/tpierrain/kenjaku/update-enginenpx skills add tpierrain/kenjaku --skill update-enginegit clone --depth 1 https://github.com/tpierrain/kenjakuWrote 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/skills/tpierrain/kenjaku/update-engine)<a href="https://agentmods.dev/skills/tpierrain/kenjaku/update-engine"><img src="https://agentmods.dev/badge/skills/tpierrain/kenjaku/update-engine.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.00087 | $0.04443 |
| Opus 5 | $0.00044 | $0.02221 |
| Sonnet 5 | $0.00017 | $0.00889 |
| Haiku 4.5 | $0.00009 | $0.00444 |
Grade A, and why
update-engine 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 4d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-engine — Upgrade your brain's engine (opt-in, non-destructive)
Brain-side skill. The engine is the machinery your brain runs on — the RAG search code (
rag/), the launchers and the engine-owned scripts. This skill swaps it for a newer version pinned in the launcher you were generated from, without ever touching what is yours: your notes,.env, constitution (CLAUDE.md),.claude/settings.json, your own skills and any engine skill you tailored are left byte-for-byte unchanged.⚠️ This is a thin conversational driver. All the real, testable work lives in the deterministic core
scripts/update-engine.mjs(ADR 0016). This skill only confirms with the user, runs the core, and reports — it holds no logic of its own.
When to use it
- The user asks to update / upgrade their brain's engine ("update your engine", "is there a new version of my brain?").
- Proactively: because the engine is observable (it records its version + where to
pull from in
engine-manifest.json), you may offer an update — but never run it without the user's explicit go-ahead, and never offer one blind: the read-only--checkin Step 1 is what turns "there might be something" into "here is what it is".
Reporting the current version? The engine version is the brain's pinned git TAG — the manifest's
source.ref(surfaced as the "Version" line ofvault_statsand on the status-line), not therag X.Y.Z/ index-schema "internal build" numbers (ADR 0017).
Golden rule — OPT-IN, NEVER automatic
Do not run the core until the user has clearly confirmed. An engine update changes code on disk and may trigger a reindex; it must always be a conscious, accepted action.
What it touches vs NEVER touches
| Updated (engine-owned) | NEVER touched (yours) |
|---|---|
rag/ search code + deps |
your notes (the whole vault/) |
rag/launch.*, scripts/run-node.* launchers |
.env (your keys) |
engine scripts (auto-commit, auto-push, status-line, verify-rag) |
CLAUDE.md (your constitution) |
update-engine itself (it self-updates) |
.claude/settings.json |
missing engine skills (e.g. local-mirror) — added if absent (ADR 0025) |
your own skills (.claude/skills/**): the engine never declared them, so it can never write them |
| engine skills you never edited: brought up to date (ADR 0026 §8) | any engine skill you tailored: kept byte-for-byte, with the engine's newer version dropped beside it as .new — and offered to you as a choice (Step 4), never silently |
missing engine MCP servers in .mcp.json — added if absent (ADR 0025) |
any server you added yourself to .mcp.json |
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.
- 4d ago First seen · 276 lines · 87 tokens per session scan A ab236b2a864c
update-engine is a skill published in the GitHub repository tpierrain/kenjaku (80 stars, last pushed 10d ago), licensed Apache-2.0. It adds 87 tokens to every session and 4,443 once invoked, about $0.0004 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 skills, from other repositories
refresh-context
Re-snapshot Core Context.md from the 9 mothership system files and key essays when the mothership changes or the snapshot is older than 30 days; also responds to /refresh-context and 코어 컨텍스트 갱신.
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…