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 agentmods add skills/keysersoose/claude-code-setup/wiki-ingestnpx skills add keysersoose/claude-code-setup --skill wiki-ingestgit clone --depth 1 https://github.com/keysersoose/claude-code-setupWrote 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/keysersoose/claude-code-setup/wiki-ingest)<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="Measured on agentmods" 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.00115 | $0.00835 |
| Opus 5 | $0.00057 | $0.00417 |
| Sonnet 5 | $0.00023 | $0.00167 |
| Haiku 4.5 | $0.00012 | $0.00084 |
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.
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
-
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 intoraw/<topic>/. - Pasted text → save verbatim as
raw/<topic>/<slug>.mdwith asource:frontmatter line. - raw/ is immutable: never edit anything already there.
- URL → fetch it; save a pointer entry (URL + date + one-line what-it-is) in
-
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.
-
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.
- Cross-project knowledge →
-
Propagate. Update
index.mdif 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. -
Log + commit. Append to today's log:
## [YYYY-MM-DD] ingest | <domain/project> | <source title>with 2-3 bullets. Thengit -C <WIKI> add -A && git commit -m "ingest: <source title>".
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.
- 5d ago First seen · 50 lines · 115 tokens per session scan A 5d6148640322
wiki-ingest is a skill published in the GitHub repository keysersoose/claude-code-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 835 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…