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 atman-33/workhub --skill kb-ingestgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/kb-ingest)<a href="https://agentmods.dev/skills/atman-33/workhub/kb-ingest"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/kb-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.00052 | $0.04308 |
| Opus 5 | $0.00026 | $0.02154 |
| Sonnet 5 | $0.00010 | $0.00862 |
| Haiku 4.5 | $0.00005 | $0.00431 |
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 4d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Ingest — Inbox Intake + Classification + Linking
Process new documents into the workhub vault. Reads content, classifies into the right zone, plans a folder-first destination and canonical filename, generates metadata, creates wikilinks, updates related documents, maintains indexes — and proposes tasks for actionable items.
Vault zones (classification targets)
| Zone | Contents |
|---|---|
inbox/ |
raw input landing zone — the default ingest source |
projects/<name>/ |
notes tied to an active project (deliverables, design notes) |
knowledge/<topic>/ |
durable reference knowledge, organized by topic |
archive/ |
completed, historical, or inactive material |
journal/ |
daily/weekly notes — never an ingest target or source |
tasks/ |
task board — actionable items become tasks (see TASK step) |
Usage
/kb-ingest # Process all eligible files in inbox/
/kb-ingest path/to/file.md # Process a specific file
/kb-ingest path/to/folder/ # Process all eligible .md files in a folder
/kb-ingest --unattended [--stale-days N] [--exclude <dir>,...]
# Headless mode for scheduled/automated runs:
# only stale files, auto-file the unambiguous,
# log the rest as pending-review (see below)
Structural README Exception
- Treat
inbox/**/README.mdas structural guidance notes, not ingest candidates. - Exclude these README files from default inbox scans and folder-based batch ingest.
- If one is passed explicitly, stop and ask the user before any move, rename, frontmatter, summary, wikilink, backlink, or index action.
Execution Flow
For each document to ingest:
1. READ
- Read full document content
- Extract existing frontmatter (preserve if present)
- Identify document type: note, reference, meeting, idea, log, paper, etc.
- Note content length (affects summarization decision)
2. ANALYZE
- Read relevant
_index.mdfiles for context (NOT full documents — token-efficient) - Determine classification:
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.
- 4d ago First seen · 384 lines · 52 tokens per session scan A 2ee6d59fe421
kb-ingest is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 4,308 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
knowledge-curator
Use when the user asks to organize notes, documents, references, or project knowledge into a searchable and maintainable structure. Inspect existing taxonomy and provenance first, preserve source meaning, mark uncertainty, and validate links and coverage after any authorized change.
wiki-ingest
Use when the user wants to ingest external sources into the vault — PDFs, markdown files, transcripts, Readwise exports, or any document. Triggers on "ingest", "process document", "import into vault", "distill this", "add to vault", or "extract knowledge from".
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
migrate
Scan the project and migrate existing documentation into OKF format. Use when the user wants to populate the knowledge base from existing docs, README, schemas, API specs, runbooks, or any structured project knowledge. Trigger on "migrate to okf", "populate the knowledge base", "scan my docs", "convert docs to okf"…
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.