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/answer)<a href="https://agentmods.dev/skills/ignromanov/llm-obsidian-wiki/answer"><img src="https://agentmods.dev/badge/skills/ignromanov/llm-obsidian-wiki/answer.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.1 | $0.00066 | $0.00833 |
| Opus 5 | $0.00033 | $0.00417 |
| Sonnet 5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
answer 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer — Query + Cite
Purpose
Answer user questions using only the wiki/ subtree as the source of truth. Compose answers with [[wikilink]] citations. For non-trivial questions, save synthesis to wiki/synthesis/<topic>.md.
Used by wiki-advisor only.
Trigger phrases
- "what do we know about X"
- "what did we decide about Y"
- "answer from the wiki"
- "find in vault"
- "summarize what's filed under Z"
Inputs
- User question (free text)
Outputs
- Inline answer with
[[wikilink]]cites - Optionally:
wiki/synthesis/<slug>.md(if non-trivial: ≥3 source pages OR new framing)
Hard contract
- READ ONLY from
wiki/, NEVER fromraw/ - DO NOT use WebFetch / WebSearch
- DO NOT fabricate — if knowledge absent, flag "wiki-researcher should be invoked"
- DO NOT edit pages outside
wiki/synthesis/
Workflow
-
Parse intent:
- Factual ("what is X") → retrieve concept + cite
- Comparative ("X vs Y") → retrieve comparison page or build synthesis
- Decision-needed ("which should I use") → retrieve decision pages, surface trade-offs
-
Hub-route:
- Start at
wiki/index.md - Identify domain hub (
wiki/<cluster>.md) - Drill to relevant concepts/decisions
- Start at
-
Multi-stage retrieval with claim-level granularity:
${CLAUDE_PLUGIN_ROOT}/scripts/wiki-search.sh --vault $VAULT_PATH --query "<query>"- For each candidate page, read
key_claimsfirst - Read full body only if claims insufficient
-
Compose answer:
- State conclusion concisely
- Each non-trivial claim followed by
[[wikilink]] - Hedge with confidence: "according to [[X]] (confidence: medium)..."
- Surface contradictions explicitly: "but [[Y]] disagrees on..."
- Surface open questions: "open question — see [[Z]]"
-
If non-trivial (≥3 source pages OR new cross-page synthesis):
- Write
wiki/synthesis/<slug>.mdwithfiled_from_query: <YYYY-MM-DD>andkey_claims - Add to hot.md:
update-hot.sh --section operation --content "wiki-advisor: filed synthesis on <topic>"
- Write
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.
- 8d ago First seen · 93 lines · 66 tokens per session scan A 457ea39bdd5b
answer is a skill published in the GitHub repository ignromanov/llm-obsidian-wiki (19 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 833 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…