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-capture-pipelinegit 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-capture-pipeline)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-capture-pipeline"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-capture-pipeline/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-capture-pipeline"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-capture-pipeline.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.00071 | $0.01069 |
| Opus 5.5 | $0.00028 | $0.00428 |
| Sonnet 5.5 | $0.00014 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
llm-wiki-capture-pipeline 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki Capture Pipeline
Goal
Design the capture architecture that makes source capture fast, safe and reviewable across channels.
When to use
- The user wants an inbox/raw topology, metadata contract or dedupe boundary designed for LLM-Wiki capture.
- The user asks for a named-channel connector runbook (Telegram, email, Slack, Discord, Teams, browser clips, voice notes, PDFs, GitHub).
- The user needs the triage handoff between capture and
wiki-triage/wiki-ingestdefined. - The user is setting privacy defaults or prompt-injection isolation rules for captured content.
- The user is adding a new high-volume or low-confidence capture channel class to an existing vault/repo.
Core rule
Capture should require near-zero filing decisions. Put material into inbox/ or raw/ first; use wiki-triage and wiki-ingest later.
Inputs
- Desired capture channel classes.
- Existing vault/repo path.
- Local-first/privacy requirements.
- Target agent and automation environment.
- Whether the output should stop at architecture or include named-channel connector rules.
Capture channel classes
Use classes here, not connector runbooks:
- manual quick capture;
- durable documents and sources;
- media assets;
- high-volume message streams;
- meeting or transcript streams;
- repo or ticket-system events.
Procedure
1. Choose capture boundary
Use one of:
| Boundary | Use when |
|---|---|
inbox/ |
Material is messy, low-confidence or not yet worth ingestion. |
raw/sources/ |
Source is trusted and should be preserved. |
raw/assets/ |
Images, audio, screenshots, diagrams, media. |
| external event log | High-volume streams that need dedup/retry before writing files. |
2. Define the shared source envelope
Every captured item should include:
captured_at: YYYY-MM-DDTHH:mm:ssZ
capture_channel: web|voice|telegram|email|chat|manual|github|other
source_url: ""
source_author: ""
source_channel: ""
source_hash: ""
privacy: public|internal|sensitive
triage_status: new
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 · 158 lines · 71 tokens per session scan A c2453c6e2906
llm-wiki-capture-pipeline is a skill published in the GitHub repository po4yka/llm-wiki-skills (4 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,069 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…
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.
wiki-export
Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…
wiki-query
Answer a question using ONLY the existing wiki vault as the knowledge base — no web search, no general LLM knowledge. Reads hot.md first (cheap recent context), then catalog.md to navigate, then drills into specific pages, then optionally semantic-searches the wiki, and synthesizes an answer with citations. Use when…