wiki-ingest

A process for adding a source document to a wiki knowledge base, including summaries, linked entities, concepts, and an index entry.

In plain words
What is it for?
Use it to ingest articles, research papers, bookmarks, and voice notes, create or update related pages, check metadata and links, and record the operation.
Why use it?
It turns a document into organized, searchable wiki knowledge instead of leaving information in an isolated file.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/darkcodepe/brainstem/wiki-ingest
Any agent
npx skills add DarkCodePE/brainstem --skill wiki-ingest
Clone the repo
git clone --depth 1 https://github.com/DarkCodePE/brainstem

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00457
Opus 5 $0.00007 $0.00229
Sonnet 5 $0.00003 $0.00091
Haiku 4.5 $0.00001 $0.00046

Measured yesterday against content hash b25705b23486, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

src/wiki_agent/skills/wiki-ingest/SKILL.md · 61 lines

What it actually says

wiki-ingest

Process a source document through the full ingest pipeline.

Steps

  1. Read the source document from raw/
  2. Classify the source type (article, paper, bookmark, voice_note)
  3. Generate a summary page at wiki/sources/<slug>.md
  4. Extract and create/update entity pages at wiki/entities/
  5. Extract and create/update concept pages at wiki/concepts/
  6. Add entries to wiki/index.md
  7. Append operation details to wiki/log.md

Quality checks

  • Every page has valid YAML frontmatter (type, title, date, sources, tags, origin)
  • type is the OKF-mandatory field (ADR-045 §9.2); write_page injects it by folder if omitted
  • Every entity/concept mention uses [[wikilink]] syntax
  • Summary is factual and traces to the source document
  • Index is updated with all new pages
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.

  1. yesterday First seen · 61 lines · 14 tokens per session scan A b25705b23486

Subscribe to this mod's changes

wiki-ingest is a skill published in the GitHub repository DarkCodePE/brainstem (1 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 457 once invoked, about $0.0001 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.