Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rvk7895/llm-knowledge-basesnpx agentmods add skills/rvk7895/llm-knowledge-bases/kb-initWrote 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/rvk7895/llm-knowledge-bases/kb-init)<a href="https://agentmods.dev/skills/rvk7895/llm-knowledge-bases/kb-init"><img src="https://agentmods.dev/badge/skills/rvk7895/llm-knowledge-bases/kb-init.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.00057 | $0.03439 |
| Opus 5 | $0.00028 | $0.01720 |
| Sonnet 5 | $0.00011 | $0.00688 |
| Haiku 4.5 | $0.00006 | $0.00344 |
Grade A, and why
kb-init 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 8d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
One-time (or re-runnable) setup that bootstraps a knowledge base project as an Obsidian vault with full omni-document support.
Prerequisites
Obsidian must be installed.
Plugin Setup
After confirming the vault path, run the bundled setup script via Bash tool:
# Interactive — asks user about each optional plugin
bash plugins/kb/setup.sh /path/to/vault
# Install everything
bash plugins/kb/setup.sh /path/to/vault --all
# Install specific plugins only
bash plugins/kb/setup.sh /path/to/vault --only dataview,obsidian-git
Required plugins (always installed):
- Dataview — query wiki articles like a database
- Obsidian Git — auto-backup vault to git
Optional plugins (user chooses interactively):
- Kanban — track wiki tasks on boards
- Outliner — better list editing for article drafts
- Tag Wrangler — rename and merge tags across the wiki
- Local Images Plus — download and store remote images locally
Browser extension (printed as manual step):
- Web Clipper — clip web articles into
raw/
The script is idempotent — safe to re-run. If Obsidian is open, tell the user to restart it.
Flow
1. Vault Setup
Ask: create a new vault or use an existing directory? If new, scaffold .obsidian/. If existing, verify it exists.
2. Source Gathering Strategy
Ask how the user wants to get raw data in:
- Self-serve -- User drops files in
raw/. Per-type guidance:- Web articles: Obsidian Web Clipper extension ->
raw/articles/ - Academic papers (PDF): Download to
raw/papers/ - GitHub repos: Clone/snapshot to
raw/repos/ - Local markdown/text: Copy to
raw/notes/ - Images/diagrams/posters: Place in
raw/images/ - YouTube transcripts: Transcript tool ->
raw/transcripts/ - Podcast episodes: Audio files ->
raw/transcripts/ - Slide decks (.pptx): Place in
raw/articles/ - Datasets (CSV, JSON): Place in
raw/datasets/ - Jupyter notebooks: Place in
raw/repos/ - X/Twitter posts: Via Smaug (optional) ->
raw/articles/
- Web articles: Obsidian Web Clipper extension ->
- Assisted -- Claude fetches via WebFetch, Bash (clone repos, download PDFs, pull transcripts, fetch YouTube subtitles)
- Mixed -- Some of each
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.
- 8d ago First seen · 375 lines · 57 tokens per session scan A 400746f87aef
kb-init is a skill published in the GitHub repository rvk7895/llm-knowledge-bases (36 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 3,439 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-08-30.
Other skills, from other repositories
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
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.
superbrain-recall
Search the user's SuperBrain second-brain vault. Use whenever the user references past work, prior decisions, "how did we", "did we already", earlier sessions, a project's history, or anything that may already be recorded — before answering from scratch.
vault-update
Incrementally update an existing vault — detect code changes via git diff and static file changes via SHA256, then re-analyze and rewrite only affected pages.