Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ignromanov/llm-obsidian-wiki/plugin install llm-obsidian-wikiWrote 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/ignromanov/llm-obsidian-wiki/migrate)<a href="https://agentmods.dev/skills/ignromanov/llm-obsidian-wiki/migrate"><img src="https://agentmods.dev/badge/skills/ignromanov/llm-obsidian-wiki/migrate/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/skills/ignromanov/llm-obsidian-wiki/migrate"><img src="https://agentmods.dev/badge/skills/ignromanov/llm-obsidian-wiki/migrate.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.00050 | $0.00604 |
| Opus 5 | $0.00025 | $0.00302 |
| Sonnet 5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
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 10d 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.
What it actually says
Migrate — Schema Upgrade
Purpose
Run schema migration scripts to upgrade vault from current schema_version to target. Idempotent. Backup-first.
Used by wiki-curator.
Trigger phrases
- "migrate wiki"
- "upgrade schema to v0.4.0"
- "apply migration"
- "schema version mismatch"
Inputs
--targetschema_version (default = latest plugin version)
Outputs
- Vault upgraded with bumped
schema_version - Migration log in
wiki/_logs/migration-<chain>-<date>.md - Backup at
<vault>.bak.v<old>/
Workflow
-
Read current schema_version from
wiki.config.md:current=$(lib_read_yaml_key "$VAULT_PATH/wiki.config.md" schema_version) -
Determine target version:
- If
--targetprovided, use it - Else use plugin version from
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json
- If
-
Find migration chain:
- Available scripts:
scripts/migrations/v<X>-to-v<Y>/migrate.sh - Build chain from current → target (e.g., 0.1.0 → 0.2.0 → 0.3.0 → 0.4.0)
- If no chain exists, error
- Available scripts:
-
Run scripts in order, idempotent:
for migration in chain: "$migration" --vault "$VAULT_PATH" -
Verify post-conditions: each migration script does its own verify; in addition, run
auditskill at the end. -
Print summary with chain executed, pages affected, log location.
Quality gate
- Each migration idempotent (re-run = no-op)
- Backup exists at
<vault>.bak.v<old>/ - Post-migration audit reports 0 P0 violations introduced
Anti-patterns
- DO NOT skip the backup
- DO NOT manually edit
schema_versionfield — only via migration scripts - DO NOT try to migrate non-linearly (skip versions)
Scripts used
${CLAUDE_PLUGIN_ROOT}/scripts/migrations/v0.1.0-to-v0.2.0.sh${CLAUDE_PLUGIN_ROOT}/scripts/migrations/v0.2.0-to-v0.3.0.sh${CLAUDE_PLUGIN_ROOT}/scripts/migrations/v0.3.0-to-v0.4.0/migrate.sh- After:
auditskill for verification
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.
- 10d ago First seen · 75 lines · 50 tokens per session scan A 6f5e47e5b91c
migrate is a skill published in the GitHub repository ignromanov/llm-obsidian-wiki (19 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 604 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…