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 DarkCodePE/brainstem --skill wiki-ingestgit clone --depth 1 https://github.com/DarkCodePE/brainstemWrote 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/darkcodepe/brainstem/wiki-ingest)<a href="https://agentmods.dev/skills/darkcodepe/brainstem/wiki-ingest"><img src="https://agentmods.dev/badge/skills/darkcodepe/brainstem/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/darkcodepe/brainstem/wiki-ingest"><img src="https://agentmods.dev/badge/skills/darkcodepe/brainstem/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.00014 | $0.00457 |
| Opus 5.5 | $0.00006 | $0.00183 |
| Sonnet 5.5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 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.
What it actually says
wiki-ingest
Process a source document through the full ingest pipeline.
Steps
- Read the source document from
raw/ - Classify the source type (article, paper, bookmark, voice_note)
- Generate a summary page at
wiki/sources/<slug>.md - Extract and create/update entity pages at
wiki/entities/ - Extract and create/update concept pages at
wiki/concepts/ - Add entries to
wiki/index.md - Append operation details to
wiki/log.md
Quality checks
- Every page has valid YAML frontmatter (type, title, date, sources, tags, origin)
typeis 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
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 · 61 lines · 14 tokens per session scan A b25705b23486
wiki-ingest is a skill published in the GitHub repository DarkCodePE/brainstem (1 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 457 once invoked, about $0.0001 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
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-export
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.
wiki-query
Search and synthesize answers from the compiled Obsidian wiki, including cited and multi-hop answers. Use for questions about existing wiki knowledge or fast index-only lookups, and for challenge requests ("challenge this", "argue against X", "poke holes in my plan") that look for the vault's own evidence against a…
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
cross-linker
Find and add missing cross-references between wiki pages. Use when pages are disconnected or after large ingestion. This modifies pages to add links; use wiki-lint for report-oriented structural auditing.