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/atman-33/workhub/vault-migratenpx skills add atman-33/workhub --skill vault-migrategit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/vault-migrate)<a href="https://agentmods.dev/skills/atman-33/workhub/vault-migrate"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/vault-migrate.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.00022 | $0.01245 |
| Opus 5 | $0.00011 | $0.00622 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
vault-migrate 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Migrate — copy another Obsidian vault into the workhub vault
Migrate the contents of a source Obsidian vault into the workhub vault's
zones. The single invariant is copy-only: the source vault is never
modified, moved, or deleted — every operation is a copy, and the source
survives intact as an archive (the only file ever written there is the final
MIGRATED.md marker).
Zone definitions and note conventions are owned by the vault's CLAUDE.md
and .claude/rules/notes.md — read them first; do not restate or override
them here.
Steps
1. SURVEY the source vault
- Inventory top-level folders with file counts
(
find <src> -type f | sed 's/\/[^/]*$//' | sort | uniq -c), excluding.obsidian/. - Detect the organizing scheme (PARA numbered folders, flat, topic folders, date folders) — it drives the mapping defaults below.
- Locate: daily-notes folder, attachments/canvas/excalidraw folders,
Templates/,.claude/rules,.obsidian/config (app.json,daily-notes.json,community-plugins.json). - Flag sensitive files: anything that looks like accounts, credentials, tokens, or encrypted notes. Never read their contents beyond the first line needed to classify them.
Done when: every top-level folder is classified and the sensitive-file list is drawn up.
2. MAP source → zones and get approval
Build a mapping table. Defaults by scheme:
| Source pattern | Destination |
|---|---|
| Active project folders (incl. per-project inbox subtrees) | projects/<kebab-name>/ |
| Ongoing-domain / reference folders (PARA Areas + Resources) | knowledge/<kebab-topic>/ (translate topic names to English kebab-case) |
| Archive folders | archive/<kebab-name>/ |
| Unclassified capture folders | inbox/ (keep subfolders; /kb-ingest classifies later) |
| Daily/weekly notes | journal/ |
| Attachments, Excalidraw, canvases | attachments/ (excalidraw in a subfolder) |
| KB activity log | append to _ai/logs/kb-log.md |
| Reusable note templates | templates/ (skip ones the vault already has) |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 113 lines · 22 tokens per session scan A cbe68619494c
vault-migrate is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,245 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
tasks
Use this skill when Pioneer should create, inspect, update, reschedule, pause, resume, troubleshoot, or configure delivery for durable tasks, scheduled tasks, recurring tasks, interval tasks, cron jobs, background work, or existing task state.
kb-preferences
Use when user wants to view, update, reset, or audit report preferences stored in vault kb.yaml. Triggers on '/kb-preferences', 'update report prefs', 'change report style', 'my preferences', or when a passive reflection step in another skill needs to propose preference updates.
wiki-orchestrate
用于整理 Obsidian LLM Wiki 的统一编排入口——定位 vault → 两方只读体检 → 汇总行动计划 → 用户确认 → 按「结构→策展」编排 wiki-struct / wiki-curate 完成整理（下一步跑哪个 skill / 命令 / 参数由模型依据体检结果判断，建议性非规则）。触发语：/wiki-orchestrate（scan / set-vault）、「整理笔记库」、「跑一次编排」、「统一整理 vault」。入口自身不改内容笔记，写操作全委托子 skill 并继承其红线。.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.