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 tom5610/llm-wiki --skill ingestgit clone --depth 1 https://github.com/tom5610/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/tom5610/llm-wiki/ingest)<a href="https://agentmods.dev/skills/tom5610/llm-wiki/ingest"><img src="https://agentmods.dev/badge/skills/tom5610/llm-wiki/ingest.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.00067 | $0.02564 |
| Opus 5 | $0.00034 | $0.01282 |
| Sonnet 5 | $0.00013 | $0.00513 |
| Haiku 4.5 | $0.00007 | $0.00256 |
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 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest workflow
Process a raw source into the wiki via a 5-phase pipeline. Use $ARGUMENTS as the source file path if provided (e.g., /ingest raw/source-document.md).
Prerequisites — Auto-bootstrap
If the wiki infrastructure is missing, create it before proceeding. This makes /ingest the only command a new user needs.
-
Check for
wiki/directory structure. If any of these are missing, create them:raw/,wiki/,wiki/concepts/,wiki/techniques/,wiki/entities/,wiki/synthesis/.llm-wiki/lenses/(lens metadata directory)
-
Check for
wiki/index.md. If missing, create with empty category scaffolding:--- title: Wiki Index type: index created: YYYY-MM-DD updated: YYYY-MM-DD --- # Wiki Index ## Entities ## Concepts ### Foundational ### Derived ## Techniques ## Synthesis & Comparisons -
Check for
wiki/log.md. If missing, create with initial entry:--- title: Wiki Log type: log created: YYYY-MM-DD updated: YYYY-MM-DD --- # Wiki Log ## [YYYY-MM-DD] init | Wiki bootstrapped via first ingest Created directory structure and initial files. -
Skip
wiki/overview.mdcreation here. Phase 5 will create or update it with real content from the source — no empty placeholder needed.
If anything was created, briefly note it to the user (e.g., "Wiki infrastructure created — proceeding with ingest.") but do not pause for confirmation.
If the wiki already exists, this section is a no-op.
Phase 1: Read & Comprehend
- Verify the source file exists and is readable. If not found, list files in
raw/to help the user find the right path. Ifraw/is empty, suggest the user add a source document first. - Read the full source. For large files (>100KB or >1000 lines), read in logical chunks (sections, chapters) and accumulate context.
- Image awareness: After reading the text, scan for image references (
,![[filename]], or HTML<img>tags):- If images are found, view each one using the Read tool (which handles image files natively).
- Note what each image conveys: diagram structure, key labels, relationships, data patterns.
- Prioritize images that convey structure (flowcharts, concept maps, process diagrams) over decorative images.
- Record the file paths of substantive images (skip decorative ones). In Phase 4, each relevant wiki page should both describe the visual information in prose AND embed the original image via
(see CLAUDE.md "Image handling" for path format).
- Build a mental model: what entities, concepts, and techniques does this source introduce?
- Read
wiki/index.mdto identify overlaps with existing wiki content.
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 · 162 lines · 67 tokens per session scan A 279efd3a6eee
ingest is a skill published in the GitHub repository tom5610/llm-wiki (2 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 2,564 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
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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…