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/importnpx skills add tpierrain/kenjaku --skill importgit 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/import)<a href="https://agentmods.dev/skills/tpierrain/kenjaku/import"><img src="https://agentmods.dev/badge/skills/tpierrain/kenjaku/import.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.00131 | $0.01907 |
| Opus 5 | $0.00066 | $0.00954 |
| Sonnet 5 | $0.00026 | $0.00381 |
| Haiku 4.5 | $0.00013 | $0.00191 |
Grade A, and why
import 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/import — Re-home a previous brain's notes into this one (opt-in, non-destructive)
Brain-side skill. It brings the notes (and attachments) of a previous second brain — or any external Obsidian-style vault — into this brain's
vault/, safely. It copies only your content, never the old engine,.gitor.claude.⚠️ This is a thin conversational driver. All the real, testable work lives in the deterministic core
scripts/import-brain.mjs+scripts/lib/import-vault.mjs(ADR 0009/0019). This skill only asks for the source, shows the plan, confirms, runs the core, reindexes, and reports — it holds no logic of its own.
When to use it
Load this whenever the user wants to bring in notes from elsewhere, in plain language and in any language — no special vocabulary required:
- "importe / migre / rapatrie / récupère mes anciennes notes depuis
<chemin>" - "import / migrate / transport / recover my old (or previous) second brain"
- "I had a brain before v3 — bring its notes over"
🧬 Flavour, not a trigger (you never need to say it): we nickname this the Kenjaku move — transplanting a mind into a new vessel. It is pure lore for the README/prose. A user who has never heard of it must trigger the import with ordinary words — and they do.
Golden rule — OPT-IN, confirm before any write
The core's plan phase performs zero writes. Show the plan, then get an explicit yes before the apply phase copies anything. Importing other people's old notes into a brain is a conscious, accepted action.
What it touches vs NEVER touches
| Imported (your content) | NEVER touched |
|---|---|
the source vault's notes (.md) |
the old engine (rag/, launchers, scripts) |
| attachments (images/PDFs) travelling with them | the source's .git, .claude, .obsidian, dotfiles |
| subfolder structure + accented names (preserved) | your existing notes — a name collision is skipped, never overwritten |
demo / example notes (tags: [exemple]) — left behind |
|
this brain's .env, CLAUDE.md, settings, skills |
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 · 136 lines · 131 tokens per session scan A b8f444348968
import is a skill published in the GitHub repository tpierrain/kenjaku (80 stars, last pushed 10d ago), licensed Apache-2.0. It adds 131 tokens to every session and 1,907 once invoked, about $0.0007 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.…