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-ecosystem-registrygit 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-ecosystem-registry)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-ecosystem-registry"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-ecosystem-registry/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-ecosystem-registry"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-ecosystem-registry.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.01334 |
| Opus 5.5 | $0.00025 | $0.00534 |
| Sonnet 5.5 | $0.00013 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
llm-wiki-ecosystem-registry 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki Ecosystem Registry
Goal
Give the user a current, evidence-backed map of LLM-Wiki implementations and adjacent frameworks, then route them to the right next skill or adoption path.
When to use
- The user asks what LLM-Wiki projects or adjacent frameworks exist.
- The user wants to compare named tools (for example OpenWiki, nashsu/llm_wiki, vouch, RepoAgent, GraphRAG stacks).
- The user asks which technology is missing from their current setup or which ready-made implementation to evaluate.
- The user needs a routing recommendation between a full application, a repo-doc agent, a review-gated memory system, or a custom build.
- The registry docs (
references/docs/13-ecosystem-matrix.md) look stale and need a refresh.
Inputs
- User use case: personal wiki, research corpus, code repo, team/company knowledge, product build.
- Constraints: local-first, cloud allowed, git required, Obsidian required, review gates, MCP, CI/CD.
- Candidate tools if already named.
- Desired output: short recommendation, detailed comparison, or registry update.
Procedure
1. Re-check current facts
Browse official upstream sources before giving current claims about:
- repository activity, releases, stars, forks or issues;
- license;
- install path;
- supported model providers;
- local/cloud modes;
- output format and storage;
- MCP/API/Agent Skills support;
- review/provenance features.
Mark any unverified item as verify-before-use.
2. Classify each candidate
Use these families:
| Family | Examples | Use when |
|---|---|---|
| Full LLM-Wiki application | nashsu/llm_wiki, desktop/vault apps |
The user wants ready-made personal/research wiki UX. |
| Repo documentation agent | langchain-ai/openwiki, OpenBMB/RepoAgent |
The corpus is a codebase and coding agents need architecture/module maps. |
| Review-gated agent memory | vouchdev/vouch |
Agents should propose knowledge updates and humans approve durable writes. |
| Obsidian/local-first workflow | Obsidian plugins, Markdown/git setups | Human reading/editing of Markdown is central. |
| Compiler-first knowledge system | atomicstrata/llm-wiki-compiler, smaller compiler projects |
The user wants typed, cited, linted and exportable compiled wiki artifacts. |
| Session-transcript wiki | Pratiyush/llm-wiki |
Agent session logs are the main raw sources. |
| Graph-heavy local vault | swarmclawai/swarmvault |
Broad ingestion, graph exports, context packs and agent handoff dominate. |
| Retrieval/GraphRAG framework | Microsoft GraphRAG, LightRAG, HippoRAG, LlamaIndex/Haystack/Qdrant stacks | Retrieval quality, scale or multi-hop reasoning is the bottleneck. |
| Custom implementation | CLI, plugin, product build | Trust, UX, provenance, integration or data constraints are specific. |
What ships with it
10 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.
- references/docs/13-ecosystem-matrix.md 13 KB
- references/docs/14-technology-stack.md 21 KB
- references/docs/15-implementation-deep-dive.md 25 KB
- references/docs/16-retrieval-architecture.md 22 KB
- references/docs/17-mcp-api-integration.md 19 KB
- references/docs/18-evaluation-methodology.md 19 KB
- references/docs/19-security-threat-model.md 23 KB
- references/docs/20-ingestion-pipelines.md 18 KB
- references/docs/21-publishing-export.md 15 KB
- references/templates/source-manifest.yaml 2.2 KB
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 · 138 lines · 63 tokens per session scan A 69fb57da6279
llm-wiki-ecosystem-registry is a skill published in the GitHub repository po4yka/llm-wiki-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 1,334 once invoked, about $0.0003 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.