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 jackwener/llm-wiki --skill ingestgit clone --depth 1 https://github.com/jackwener/llm-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/jackwener/llm-wiki/ingest)<a href="https://agentmods.dev/skills/jackwener/llm-wiki/ingest"><img src="https://agentmods.dev/badge/skills/jackwener/llm-wiki/ingest/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/jackwener/llm-wiki/ingest"><img src="https://agentmods.dev/badge/skills/jackwener/llm-wiki/ingest.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.00052 | $0.00633 |
| Opus 5.5 | $0.00021 | $0.00253 |
| Sonnet 5.5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
ingest 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest an LLM Wiki source
Turn a source into concise, attributable, interconnected wiki pages. The wiki
is the maintained knowledge layer; sources/ is the immutable evidence layer.
Before editing
- Locate the vault by finding
.llm-wiki/config.toml. - Read
wiki-purpose.md,wiki-schema.md, andwiki-agent.mdwhen present. The latter defines vault-specific MUST / MAY / NEVER ingest criteria. - Skip material that the agent policy excludes, contains credentials or personal data, or duplicates existing knowledge.
- If the vault is empty, agree with the user on language, page layout, directory structure, and filename conventions before creating pages.
- If the material would change established scope, page boundaries, naming, or linking strategy, present the proposed structure before editing. Apply straightforward additions directly.
Workflow
-
Check
wiki/,wiki-log.md, andllm-wiki searchfor prior ingestion of the source or its topics. Re-ingest only changed or newly useful material. -
Copy raw input to
sources/YYYY-MM-DD/, preserving its original name. Add a version suffix if needed. Once saved, never edit that copy. Split large chat logs or collections by date or topic before saving. -
Extract claims, entities, decisions, open questions, and relationships.
-
Create or merge focused pages in
wiki/. Every page needs the fields required bywiki-schema.md; normally this includes:--- title: Page Title description: One-line summary aliases: [alternate names] tags: [taxonomy tags] sources: [YYYY-MM-DD/source.md] created: YYYY-MM-DD updated: YYYY-MM-DD ---Bug or issue pages also need machine-readable
status: open | resolved | wontfix. -
Merge rather than overwrite. When sources conflict, preserve both claims, identify their sources, and flag the conflict rather than silently choosing one.
-
Add
[[wikilinks]]for related entities, including useful not-yet-created pages, and finish each page with a## Relatedsection. -
Append a concise
## [YYYY-MM-DD] ingest | …entry towiki-log.mdwith pages created or updated. -
Run
llm-wiki syncafter the changes.
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 · 64 lines · 52 tokens per session scan A add7f32f0c66
ingest is a skill published in the GitHub repository jackwener/llm-wiki (104 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 633 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-30.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…