Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AIwork4me/open-llm-wikinpx agentmods add skills/aiwork4me/open-llm-wiki/wiki-ingestWrote 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/aiwork4me/open-llm-wiki/wiki-ingest)<a href="https://agentmods.dev/skills/aiwork4me/open-llm-wiki/wiki-ingest"><img src="https://agentmods.dev/badge/skills/aiwork4me/open-llm-wiki/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/aiwork4me/open-llm-wiki/wiki-ingest"><img src="https://agentmods.dev/badge/skills/aiwork4me/open-llm-wiki/wiki-ingest.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.00116 | $0.02459 |
| Opus 5 | $0.00058 | $0.01229 |
| Sonnet 5 | $0.00023 | $0.00492 |
| Haiku 4.5 | $0.00012 | $0.00246 |
Grade A, and why
wiki-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 10d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Ingest
Ingest one source document into an open-llm-wiki vault. Optimize for traceability, safe file changes, and independent verification rather than speed.
Runtime Tools
Prefer deterministic runtime scripts when they are available in either the repo or the vault:
<repo>/scripts/wiki_lint.py<vault>/.open-llm-wiki/scripts/wiki_lint.py<repo>/scripts/wiki_grow.py<vault>/.open-llm-wiki/scripts/wiki_grow.py<repo>/scripts/wiki_claims.py<vault>/.open-llm-wiki/scripts/wiki_claims.py<repo>/scripts/wiki_normalize_metrics.py<vault>/.open-llm-wiki/scripts/wiki_normalize_metrics.py<repo>/scripts/wiki_semantic_qa.py<vault>/.open-llm-wiki/scripts/wiki_semantic_qa.py<repo>/scripts/wiki_science_review.py<vault>/.open-llm-wiki/scripts/wiki_science_review.py<repo>/scripts/wiki_discover_sources.py<vault>/.open-llm-wiki/scripts/wiki_discover_sources.py<repo>/scripts/wiki_queue.py<vault>/.open-llm-wiki/scripts/wiki_queue.py<repo>/scripts/wiki_contradictions.py<vault>/.open-llm-wiki/scripts/wiki_contradictions.py<repo>/scripts/wiki_concept_revision.py<vault>/.open-llm-wiki/scripts/wiki_concept_revision.py<repo>/scripts/pdf_corpus_to_markdown.py<vault>/.open-llm-wiki/scripts/pdf_corpus_to_markdown.py<repo>/scripts/pdf_to_markdown.py<vault>/.open-llm-wiki/scripts/pdf_to_markdown.py<repo>/scripts/wiki_search.py<vault>/.open-llm-wiki/scripts/wiki_search.py
Run lint before and after ingest:
uv run python scripts/wiki_lint.py "<vault>" --fail-on p1
Safety Boundary
- Run only after the user explicitly asks to ingest a source.
- Process one source at a time. Do not batch ingest unless the user asks for a serial queue and confirms the order.
- Work only inside the resolved wiki vault. Never write outside
raw/,drafts/,sources/,concepts/,qa-reports/,claims/,_state/,templates/,index.md, orlog.md. - Treat
raw/as immutable evidence. Do not edit, rename, or delete source files. Write parsed text to a new file. - Use local parsing by default. Use cloud OCR only when the user has configured credentials and accepts that document content leaves the local machine.
- Before publishing or changing concept pages, summarize the planned file
changes. If the user requested a fully automated ingest, continue and record
all changes in
log.md. - Never silently overwrite a stable source page, QA report, or contradiction report. Create a new draft or ask the user how to handle the conflict.
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.
- 10d ago First seen · 267 lines · 116 tokens per session scan A 28210203453a
wiki-ingest is a skill published in the GitHub repository AIwork4me/open-llm-wiki (2 stars, last pushed 4mo ago), licensed MIT. It adds 116 tokens to every session and 2,459 once invoked, about $0.0006 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
kb-index
Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale.
second-reader
Build and run a source-verified Markdown knowledge vault (opens as an Obsidian vault). Ingests books, PDFs, transcripts, and articles into atomic, cross-linked, cited notes, then gates every note and every answer behind an independent verification pass that re-reads the source cold and loops until a round finds…
wiki-ingest
A workflow for bringing URLs, files, and pasted external material into a LoreKit knowledge collection, then saving it as wiki pages with source links and tracking records.
wiki-lint
A health-check skill for a document knowledge base, also called a corpus. It reports missing metadata, broken links, isolated pages, unreadable sources, and reviews that are overdue.
wiki-output
A workflow for creating outward-facing slides, article drafts, charts, and briefing materials from an existing knowledge base. It saves the finished materials in designated output folders.
corpus-ingest
A cross-project entry point for saving URLs, articles, PDFs, files, and other outside material into a configured LoreKit knowledge collection. It routes the work to that collection's own filing rules.