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 skills add po4yka/llm-wiki-skills --skill llm-wiki-migration-plannergit clone --depth 1 https://github.com/po4yka/llm-wiki-skillsWrote 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/po4yka/llm-wiki-skills/llm-wiki-migration-planner)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-migration-planner"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-migration-planner/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/po4yka/llm-wiki-skills/llm-wiki-migration-planner"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-migration-planner.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.00073 | $0.00823 |
| Opus 5 | $0.00036 | $0.00411 |
| Sonnet 5 | $0.00015 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
llm-wiki-migration-planner 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 12d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki Migration Planner
Goal
Produce a safe, reviewable migration plan without changing the user's files.
When to use
- The user wants a plan before migrating notes, docs, or an Obsidian vault into an LLM-Wiki, without touching any files yet.
- The user is deciding between a personal vault, repo wiki, team wiki, research corpus, or product prototype target and needs a mapping proposal first.
- The source is mixed content (Notion export, chat export, research PDFs, company docs) and needs profile-specific classification before any move happens.
- The user asks for a dry-run, review, or approval step ahead of running
llm-wiki-refactor.
Inputs
- Current document root.
- Desired target: personal vault, repo wiki, team wiki, research corpus, or product prototype.
- Existing constraints: Obsidian, Notion export, docs generator, git, privacy, attachments.
Procedure
1. Confirm dry-run mode
State that this skill produces a plan only. Do not move, rename, delete, normalize frontmatter, or rewrite links.
2. Identify migration profile
Classify the source:
| Profile | Notes |
|---|---|
| Obsidian vault | Preserve wikilinks, aliases and attachments. |
| Repository docs | Preserve README/ADR/docs generator conventions. |
| Notion export | Normalize nested pages and attachment paths. |
| Readwise/Omnivore export | Treat exports as raw sources first. |
| Chat exports | Separate raw conversation from reusable query pages. |
| Research PDFs | Preserve PDFs in raw/assets or raw/sources. |
| Company docs | Require PR-based write model and permissions. |
3. Inventory and classify
For each candidate file, infer:
- current path;
- likely page type;
- whether it is raw, wiki, synthesis, query, asset, or mixed;
- confidence;
- migration risk;
- proposed target path.
4. Build mapping table
Use this table:
| Current path | Proposed path | Type | Confidence | Risk | Notes |
|---|---|---|---:|---|---|
Use confidence values conservatively. Low-confidence rows should require human review. Re-verify each row's proposed path and confidence against the actual current file contents, not just filenames, before finalizing the table.
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.
- 12d ago First seen · 116 lines · 73 tokens per session scan A 99672f1d2d3c
llm-wiki-migration-planner is a skill published in the GitHub repository po4yka/llm-wiki-skills (3 stars, last pushed 19d ago), licensed MIT. It adds 73 tokens to every session and 823 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-31.
Other skills, from other repositories
wiki-export
Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…
template-execute
Execute a Templater template, optionally writing the rendered output to a new file. Arguments are exposed to the template via tp.mcpTools.prompt("key") (directly under tp, NOT under tp.user — easy footgun). EN triggers: "render the X template", "run the daily template", "execute Templates/X.md with arg1=v1", "use…
read-frontmatter
Read frontmatter (the whole object or one key) from a file. Types are preserved (numbers stay numbers, arrays stay arrays). EN triggers: "what's the frontmatter of X", "show me the metadata of X", "read the properties of X", "what's the status of X", "get the tags on X". FR triggers : "quel est le frontmatter de X"…
read-get
Read the full content of a file from a vault (markdown + frontmatter). EN triggers: "show me X", "open the file X", "read X", "what's in X.md", "fetch X". FR triggers : "montre-moi X", "ouvre le fichier X", "lis X", "qu'est-ce qu'il y a dans X.md", "récupère X". Example / Exemple: EN: "show me Sessions/2026-05-03.md"…
ingest
A tool for adding a URL, file, text, or Inbox item to the LLM Wiki. It checks the material's purpose, preserves the original source, compiles a wiki page, updates indexes and logs, and reviews the result.
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…