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-indexgit 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-index)<a href="https://agentmods.dev/skills/atman-33/workhub/kb-index"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/kb-index/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.
<a href="https://agentmods.dev/skills/atman-33/workhub/kb-index"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/kb-index.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.01905 |
| Opus 5.5 | $0.00020 | $0.00762 |
| Sonnet 5.5 | $0.00010 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
kb-index 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Index — Smart Index Update
Update the vault's _index.md files efficiently. By default, detects what
changed and updates only affected entries. Full rebuild available when needed.
Indexed zones and their index files:
| Zone | Index |
|---|---|
projects/ |
projects/_index.md |
knowledge/ |
knowledge/_index.md |
archive/ |
archive/_index.md |
tasks/archive/ |
tasks/archive/_index.md |
The board index tasks/_index.md and _ai/index/tasks.json are managed by the
workhub app — never rebuild them here. tasks/archive/_index.md is a different
file (a summary of completed/inactive tasks) and is managed by this
command. inbox/ and journal/ are intentionally unindexed.
Usage
/kb-index # Smart update (diff-based, fast)
/kb-index --full # Full rebuild (scan everything)
/kb-index --zone knowledge # Update one zone only
/kb-index --dry-run # Preview changes without writing
3-Tier Strategy
Choose the lightest approach that fits the situation:
Tier 1: Per-File Update (via kb-ingest) — ~200 tokens
When: A single file was ingested or moved.
How: kb-ingest already handles this — adds one line to _index.md.
No need to run kb-index separately.
Tier 2: Smart Diff Update (default kb-index) — ~500-1500 tokens
When: A few files changed, or "something feels off."
How: Compare existing _index.md entries against actual files on disk.
Only process differences. Do not re-render from
templates/_index.md.template in this mode.
Tier 3: Full Rebuild (kb-index --full) — ~3-4K tokens
When: Major reorganization, initial setup, or indexes are badly corrupted.
How: Scan everything from scratch, regenerate all indexes from
templates/_index.md.template.
Tier 2: Smart Diff — Execution Flow
This is the default behavior when you run /kb-index.
Step 1: READ existing indexes (cheap — ~200 tokens total)
Read each zone _index.md (10-20 lines each)
Extract: listed items, last updated date
Step 2: DETECT changes (cheap — tool calls only, no file reads)
For each zone:
Glob: list current subdirectories and .md files on disk
Compare against items listed in _index.md
Classify each item:
MATCH — in index AND on disk → skip (no action)
ADDED — on disk but NOT in index → needs adding
REMOVED — in index but NOT on disk → needs removing
If zero differences found:
Log "[date] index | no changes detected" → done
Step 3: PROCESS only differences
For ADDED items only:
Read the new file's overview/frontmatter (~50-100 tokens per file)
Generate one-line index entry
For REMOVED items:
Delete the line from _index.md
Skip MATCH items entirely — don't re-read, don't regenerate
Step 4: UPDATE indexes
Edit (not rewrite) each affected _index.md:
Insert new entries, remove deleted entries
Update summary count line
Update "updated: {today}" in frontmatter
Step 5: LOG
Append to _ai/logs/kb-log.md:
"[date] index-update | added N, removed M | touched K zones"
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.
- 1mo ago First seen · 206 lines · 51 tokens per session scan A 53cd7a4bafda
kb-index is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,905 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…
curator-practice
Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs…
memo-writing
How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on /memex:save, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the [memex] activity nudge appears in context. Do NOT trigger for…
recall
Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do…
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.