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 wiki-querygit 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/wiki-query)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/wiki-query"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/wiki-query/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/wiki-query"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/wiki-query.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.00047 | $0.00910 |
| Opus 5.5 | $0.00019 | $0.00364 |
| Sonnet 5.5 | $0.00009 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
wiki-query 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Query
Goal
Answer from the compiled wiki first, verify against raw sources when needed, and save reusable answers back into the wiki.
When to use
- The user asks a question answerable from the existing vault.
- Research, synthesis, comparison or decision support should reuse wiki knowledge.
- A reusable answer should be filed back into the wiki.
A filled question-to-answer example ships in assets/worked-example.md.
Inputs
- User question.
wiki/index.md.- Relevant wiki pages.
- Raw sources when verification is required.
- Optional output format: memo, table, checklist, PRD, slides outline, report.
Write permissions
Allowed:
- read all wiki files;
- read raw sources when needed;
- create
wiki/queries/*for reusable answers; - create draft
wiki/synthesis/*only when requested or clearly useful; - append to
wiki/log.mdwhen saving an answer.
Not allowed unless explicitly requested:
- rewrite existing source/entity/concept pages;
- mark claims verified;
- edit protected human-owned sections;
- delete or archive pages.
Procedure
1. Clarify the question internally
Identify the answer type, time sensitivity, verification needs and whether the answer should be saved. Do not ask a clarifying question when the best effort is obvious.
2. Start with the map
Read wiki/index.md first and identify candidate pages.
3. Search the wiki
Use exact search for user terms, synonyms, entity names, wikilink targets, frontmatter types and tags. Prefer focused reads over loading many full files.
4. Build an evidence set
For each important claim, classify support:
extracted | inferred | ambiguous | synthesis | unsupported | conflicting
Use raw sources when the claim is high-impact, current, legal/financial/medical/security-relevant, or the wiki page is stale.
5. Answer clearly
Distinguish:
- what the wiki says;
- what is directly sourced;
- what is inferred;
- what remains uncertain;
- what should be checked next.
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.
- 1mo ago First seen · 135 lines · 47 tokens per session scan A 6add5a6f8b43
wiki-query is a skill published in the GitHub repository po4yka/llm-wiki-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 910 once invoked, about $0.0002 per session on Opus 5.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
obsidian-memory
Explicit-only Obsidian memory workflow. Use when the user explicitly asks to work with an Obsidian vault, LLM wiki, agent memory, RAW/source ingest, provenance, QUERY, LINT, or release safety for a markdown knowledge system. Do not auto-route ordinary coding sessions into external vault workflows.
wiki-lint
Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…
okf-harness-bootstrap
This unified entrypoint routes setup and workspace maintenance without making the user choose a mode.
meta-sync-template
Interactive flow to propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing obsidian-local-rest-api upfront, lets the user pick all or a subset, and optionally re-clones…
save
File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…
librarian
Orchestrate vault knowledge workflows using the Librarian MCP server. Ingest solutions, search prior art, explore the knowledge graph, log daily learnings.