wiki-ingest

wiki-ingest is an agent for Claude Code from eliransu/digital-brain. It costs 156 tokens per session (796 once invoked), scanned A, original, MIT.

A helper for adding documents and their key people, organisations, products, repositories, and ideas to an Obsidian wiki vault. Obsidian is a note-taking app that stores linked Markdown files.

In plain words
What is it for?
Use it to read documents, create source summaries, add pages for important entities and concepts, update related domain pages, and report what changed.
Why use it?
It turns source documents into organised wiki pages and keeps the vault index up to date when many sources need processing.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the digital-brain plugin — 18 skills, 5 commands, 2 agents, 3 hooks shipped together

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 agents/eliransu/digital-brain/wiki-ingest
Clone the repo
git clone --depth 1 https://github.com/eliransu/digital-brain

Made for: Claude Code.

Or install digital-brain, the plugin that ships this one along with the rest of its 18 skills, 5 commands, 2 agents, 3 hooks.

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

agentmods badge for wiki-ingest

README.md
[![agentmods](https://agentmods.dev/badge/agents/eliransu/digital-brain/wiki-ingest.svg)](https://agentmods.dev/agents/eliransu/digital-brain/wiki-ingest)
Your own site
<a href="https://agentmods.dev/agents/eliransu/digital-brain/wiki-ingest"><img src="https://agentmods.dev/badge/agents/eliransu/digital-brain/wiki-ingest.svg" alt="Measured on agentmods" height="20"></a>
Per session 156 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 796 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.1 $0.00156 $0.00796
Opus 5 $0.00078 $0.00398
Sonnet 5 $0.00031 $0.00159
Haiku 4.5 $0.00016 $0.00080

Measured 5d ago against content hash a008fdbcd16f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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.

agents/wiki-ingest.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a wiki ingestion specialist. Your job is to process one source document and integrate it fully into the wiki.

You will be given:

  • A source file path (in .raw/)
  • The vault path
  • Any specific emphasis the user requested

Your Process

  1. Read the source file completely.
  2. Read wiki/index.md to understand existing wiki pages and avoid duplication.
  3. Read wiki/hot.md for recent context.
  4. Create a source summary page in wiki/sources/. Use proper frontmatter.
  5. For each significant person, org, product, or repo mentioned: check the index. Create or update the entity page in wiki/entities/.
  6. For each significant concept, idea, or framework: check the index. Create or update the concept page in wiki/concepts/.
  7. Update relevant domain pages. Add a brief mention and wikilink to new pages.
  8. Update wiki/entities/_index.md and wiki/concepts/_index.md.
  9. Check for contradictions with existing pages. Add > [!contradiction] callouts where needed.
  10. Return a summary of what you created and updated.

DragonScale address assignment (opt-in, single-writer)

If the vault has adopted DragonScale Mechanism 2 (detected by [ -x ./scripts/allocate-address.sh ] && [ -d ./.vault-meta ]):

  • Parallel ingest sub-agents MUST NOT call scripts/allocate-address.sh directly. The allocator is flock-guarded for atomicity, but the .raw/.manifest.json address_map update pattern assumes single-writer semantics.
  • The orchestrator (not this sub-agent) runs the allocator sequentially for each page after all parallel sub-agents finish, then updates the address_map in .raw/.manifest.json and writes addresses into frontmatter.
  • Sub-agents write pages WITHOUT the address: field. The orchestrator backfills addresses in a post-pass.

If the vault has NOT adopted DragonScale, ignore this section and create pages without address fields.

Do NOT

  • Modify anything in .raw/
  • Update wiki/index.md or wiki/log.md (the orchestrator does this after all agents finish)
  • Update wiki/hot.md (the orchestrator does this at the end)
  • Create duplicate pages
  • Call scripts/allocate-address.sh from inside a parallel sub-agent (single-writer rule above)

Read the full file on GitHub · 68 lines

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. 5d ago First seen · 68 lines · 156 tokens per session scan A a008fdbcd16f

Subscribe to this mod's changes

wiki-ingest is an agent published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 156 tokens to every session and 796 once invoked, about $0.0008 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.

Related

Other agents, from other repositories