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 NimaChu/my-wiki --skill my-wiki-skillgit clone --depth 1 https://github.com/NimaChu/my-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/nimachu/my-wiki/my-wiki-skill)<a href="https://agentmods.dev/skills/nimachu/my-wiki/my-wiki-skill"><img src="https://agentmods.dev/badge/skills/nimachu/my-wiki/my-wiki-skill/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/nimachu/my-wiki/my-wiki-skill"><img src="https://agentmods.dev/badge/skills/nimachu/my-wiki/my-wiki-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.04340 |
| Opus 5 | $0.00039 | $0.02170 |
| Sonnet 5 | $0.00016 | $0.00868 |
| Haiku 4.5 | $0.00008 | $0.00434 |
Grade A, and why
my-wiki 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Wiki
This Skill is a thin Agent adapter, not the My Wiki application. Use its bundled scripts/my-wiki.mjs bridge, which locates and invokes a separately installed My Wiki project. Never expect application code, Dashboard assets, or a knowledge vault to live inside the installed Skill.
Use native OKF terminology in user-facing explanations and new knowledge: Concept means a durable synthesized page under concepts/, Reference means captured evidence under references/sources/, and original means its preserved snapshot or binary under references/originals/. My Wiki displays Concepts as concept planets. Legacy command names and internal fields such as organize-raw, rawSources, wikiPages, export-universe, and workflow_status remain compatibility APIs; they do not restore the old raw/ or wiki/ layout.
Before the first operation, run the bridge with where. If it reports that the My Wiki project is missing, explain that both components are required and ask the user before cloning or registering the project. The normal setup is:
git clone https://github.com/NimaChu/my-wiki.git
cd my-wiki
npm run setup
An existing checkout can instead be selected with MY_WIKI_HOME=/path/to/my-wiki. Do not silently install, update, or relocate the project.
After the user confirms the project location, the Agent may perform the clone and npm run setup on the user's behalf. Then ask where the local vault should live and run init for them. A separately installed Skill must therefore be able to guide and complete both missing layers, but only with explicit user confirmation; the Skill package itself remains a small adapter and never embeds either layer.
Bootstrap Missing Layers
Use this flow only when the bridge reports a missing layer; do not repeat it during normal operations:
- Missing project: Explain that the Skill is an adapter and ask where the user wants the standalone project installed. After confirmation, clone
https://github.com/NimaChu/my-wiki.gitinto that location and runnpm run setupfrom the cloned repository. Do not overwrite an existing directory or silently choose a different location. - Existing project: If the user already has a checkout, register it by running
npm run setupthere or setMY_WIKI_HOMEwhen they explicitly prefer an environment-only configuration. Never clone a duplicate project merely because it is not registered. - Missing vault: Rerun
where. If no vault is configured, ask where local knowledge should live, then run the bridge'sinit <path> --name <name> --use. Keep the vault outside both the project and installed Skill. - Verify: Run
whereandstatusthrough the bridge. Continue with the user's original request only after both resolve successfully.
What ships with it
8 files 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.
- 9d ago First seen · 132 lines · 78 tokens per session scan A 0903ff0de8ff
my-wiki is a skill published in the GitHub repository NimaChu/my-wiki (123 stars, last pushed 10d ago), licensed MIT. It adds 78 tokens to every session and 4,340 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
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
vault-for-llm
Connect OpenClaw to Vault Agent Memory as a local-first governed project memory layer. Search first, then bounded-read cited source ranges; propose new memories as candidates instead of writing directly into active memory.