kb-ingest

A workflow for downloading an external documentation website or local documentation folder into a personal knowledge base. It stores the downloaded material as a document pack with a manifest and source note.

In plain words
What is it for?
Use it to ingest provider, tooling, protocol, language, or library documentation from a URL or local directory, optionally limiting which pages and content sections are copied.
Why use it?
It avoids repeatedly browsing the same reference material and keeps imported documentation organized with its source and version information.

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/kelp/agent-plugins/kb-ingest
Any agent
npx skills add kelp/agent-plugins --skill kb-ingest
Clone the repo
git clone --depth 1 https://github.com/kelp/agent-plugins

Made for: Claude Code, Codex.

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,349 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.00078 $0.02349
Opus 5 $0.00039 $0.01175
Sonnet 5 $0.00016 $0.00470
Haiku 4.5 $0.00008 $0.00235

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

Security

Grade A, and why

kb-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 2d 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.

plugins/knowledge-forge/skills/kb-ingest/SKILL.md · 331 lines

How it starts

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

/kb-ingest

Download an external documentation site into the personal knowledge base as a doc pack and source note. Safe to run from any working directory.

Input

Scope: $ARGUMENTS

Two forms:

Web crawl: <url> [category] [tool] [version] [path_prefix] [selector]

Local copy: <local-path> [category] [tool] [version]

  • url or local-path — required. An https:// URL to crawl, or an absolute/relative path to a local directory of already-downloaded docs.
  • category — optional. Where in raw/external/ to file the pack (e.g. providers, tooling, protocols, languages, libraries).
  • tool — optional. Tool/service name slug (e.g. fastmail, jmap, uv).
  • version — optional. Defaults to latest.
  • path_prefix — optional (web only). Limits crawl to URLs with this prefix. Leave empty to crawl from root.
  • selector — optional (web only). CSS selector for content extraction. Defaults to main.

Step 1: Resolve the KB path

Run ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-kb-path.sh and capture its stdout as kb_path. Every subsequent command uses "$kb_path" (double-quoted).

kb_path=$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-kb-path.sh")

If the script exits non-zero, relay its stderr message to the user verbatim and stop — do not guess a fallback path.


Step 2: Parse arguments and classify

Extract the first token from $ARGUMENTS. Detect mode:

  • If it starts with /, ~/, or ./local mode (copy from a local directory; skip the web crawl)
  • Otherwise → web mode (crawl from the URL)

In local mode, resolve the source path:

src_path=$(realpath "$first_token" 2>/dev/null)
[ -d "$src_path" ] || { echo "Source path not found"; exit 1; }

If category and tool are not provided, derive them from the URL domain (web mode) or ask once (local mode):

Domain category tool
fastmail.com providers fastmail
jmap.io protocols jmap
anthropic.com providers anthropic
openai.com providers openai
docs.*.com or similar ask ask

Read the full file on GitHub · 331 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. 2d ago First seen · 331 lines · 78 tokens per session scan A c982b1ad78df

Subscribe to this mod's changes

kb-ingest is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 78 tokens to every session and 2,349 once invoked, about $0.0004 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 skills, from other repositories

dummy-dataset

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.

phuryn/pm-skills · 48 tokens

outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

phuryn/pm-skills · 53 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

shipping-artifacts

The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…

phuryn/pm-skills · 120 tokens

competitive-battlecard

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.

phuryn/pm-skills · 52 tokens