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-faqgit 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-faq)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-faq"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-faq/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-faq"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-faq.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.00063 | $0.03406 |
| Opus 5 | $0.00032 | $0.01703 |
| Sonnet 5 | $0.00013 | $0.00681 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
llm-wiki-faq 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki FAQ
Goal
Give users concrete, evidence-aware answers to common LLM-Wiki adoption questions without overclaiming. Prefer practical operating models over hype.
When to use
Use when the user asks:
- "Why do I need this?"
- "What benefits will I get?"
- "Is there evidence this works?"
- "Is this better than RAG?"
- "How do I keep it alive?"
- "Do I need Obsidian?"
- "Is this just another note-taking system?"
- "Will this become slop?"
- "What should I measure?"
- "I am not a developer; how would I use this?"
- "Why should I deal with PRs/MRs when Confluence only needs a browser?"
- "Will the wiki fit in the model context as it grows?"
- "Is this knowledge for agents or humans?"
- "What content can I upload, and what about sensitive data?"
- "Where should I start?"
- "When should I not use it?"
- "Who owns or reviews the wiki?"
- "How much time or money will this take?"
- "How do I prove ROI?"
- "Does this replace Confluence, Notion, SharePoint, RAG or search?"
- "How do I migrate safely?"
- "What if the agent is wrong?"
- "How do permissions, vendor lock-in, link rot or multi-agent access work?"
- "What are the strongest arguments against this?"
- "Will this hurt my own understanding?"
- "Will this become a write-only archive?"
Inputs
- The stakeholder's question or objection, in their own words (e.g. "Is this better than RAG?", "Do I need Obsidian?").
- Context about the target wiki: greenfield vs already migrating, team size, whether git/PR workflows already exist.
- Whether sensitive or regulated data is involved, so the answer can route to
llm-wiki-privacy-redactororllm-wiki-model-policywhen needed. - Which bundled reference files are available under
references/(evidence-pack, adoption-objections, additional-adoption-q-and-a, criticism-pack) to ground the answer.
Required references
Read these when available:
references/evidence-pack.mdfor evidence-backed adoption arguments.references/adoption-objections.mdfor non-developer, Confluence/browser, token, human-readable, slop and sensitive-data objections.references/additional-adoption-q-and-a.mdfor start-small, ownership, cost, ROI, migration, RAG/search, lock-in and multi-agent questions.references/criticism-pack.mdfor serious criticism and mitigation answers.- Repository-level docs:
references/docs/adoption-objections.mdreferences/docs/adoption-q-and-a.mdreferences/docs/criticism-and-mitigations.md
What ships with it
7 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.
- 12d ago First seen · 329 lines · 63 tokens per session scan A 377822b51e3e
llm-wiki-faq is a skill published in the GitHub repository po4yka/llm-wiki-skills (3 stars, last pushed 19d ago), licensed MIT. It adds 63 tokens to every session and 3,406 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-31.
Other skills, from other repositories
okf-harness-bootstrap
This unified entrypoint routes setup and workspace maintenance without making the user choose a mode.
okf-harness
One Door routes OKF Harness workspace requests to exactly one internal workflow at a time.
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…
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…
wiki-boundary
Rank the "frontier" pages of a wiki — the crossroads many pages link to that stay thin inside — so you can decide where research would pay off most. Use when the user says "what should I write about next", "where are the gaps", "which pages need work", "find the thin hub pages", "boundary pages", "/wiki-boundary"…