wiki-ingest

wiki-ingest is a skill for Claude Code, Codex from keysersoose/claude-code-setup. It costs 115 tokens per session (835 once invoked), scanned A, original, MIT.

A knowledge-ingestion workflow that turns a URL, file, export, or pasted material into a cited page in a shared language-model wiki.

In plain words
What is it for?
Capture sources, read and discuss their key points, write or update wiki pages, maintain the index, and record each ingestion.
Why use it?
It preserves source material and connects its important findings to an organised knowledge base instead of leaving research scattered across files or chats.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Capture sources, read and discuss their key points, write or update wiki pages, maintain the index, and record each ingestion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/keysersoose/claude-code-setup/wiki-ingest
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.

Any agent
npx skills add keysersoose/claude-code-setup --skill wiki-ingest
Clone the repo
git clone --depth 1 https://github.com/keysersoose/claude-code-setup

Made for: Claude Code, Codex.

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/skills/keysersoose/claude-code-setup/wiki-ingest/github.svg)](https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-ingest)
Your own site
<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-ingest"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/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.

agentmods 80×15 button for wiki-ingest

Your own site · 80×15
<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-ingest"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/wiki-ingest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 835 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00115 $0.00835
Opus 5.5 $0.00046 $0.00334
Sonnet 5.5 $0.00023 $0.00167
Haiku 4.5 $0.00012 $0.00084

Measured 2mo ago against content hash 5d6148640322, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

skills/wiki-ingest/SKILL.md · 50 lines

How it starts

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

/wiki-ingest — turn a source into compounding knowledge

WIKI = the global knowledge base path defined in your global CLAUDE.md. One source per ingest, supervised — Karpathy's own practice ("ingest one at a time, stay involved to guide what to emphasize"). Ask the user ONE question only if the target domain/project is genuinely ambiguous; otherwise infer and proceed.

Steps

  1. Capture the raw source.

    • URL → fetch it; save a pointer entry (URL + date + one-line what-it-is) in raw/README.md. Don't copy full web content into raw/.
    • Local file (PDF/export/doc) → leave it where it lives if large; add a pointer in raw/README.md. Small standalone files (<1MB) may be copied into raw/<topic>/.
    • Pasted text → save verbatim as raw/<topic>/<slug>.md with a source: frontmatter line.
    • raw/ is immutable: never edit anything already there.
  2. Read and discuss. Read the source fully (delegate to a cheap subagent if it's very long; verify the load-bearing claims yourself). Surface the 3-5 takeaways that matter FOR THE USER'S CONTEXT (their projects, their business) — not a generic summary.

  3. Write the wiki page. Decide placement:

    • Cross-project knowledge → domains/<domain>.md (extend existing page if one fits — update-don't-duplicate).
    • About a person/company → people/.
    • Project-specific → that project's page, or a subpage linked from it.
    • Genuinely new topic → new page in the best-fitting folder. Page format: frontmatter (type, created, updated, tags, source), one-line summary at top, the distilled knowledge, explicit citation link to the raw source/pointer, links to related pages.
  4. Propagate. Update index.md if a new page was created (one line). Touch the 2-5 RELATED pages whose content this source changes — add a line or fix a now-wrong claim (delete-when-wrong). Don't fan out further; lint catches the rest.

  5. Log + commit. Append to today's log: ## [YYYY-MM-DD] ingest | <domain/project> | <source title> with 2-3 bullets. Then git -C <WIKI> add -A && git commit -m "ingest: <source title>".

Read the full file on GitHub · 50 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. 2mo ago First seen · 50 lines · 115 tokens per session scan A 5d6148640322

Subscribe to this mod's changes

wiki-ingest is a skill published in the GitHub repository keysersoose/claude-code-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 115 tokens to every session and 835 once invoked, about $0.0005 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.

Related

wiki-ingest compared with skills from other repositories

wiki-ingest next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
wiki-ingestkeysersoose/claude-code-setupSkill24mo agoMITA115Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code