knowledge_base

A system for storing and finding personal knowledge in a searchable graph, uploaded documents, and linked Markdown notes. Markdown is a plain-text format commonly used for notes and documentation.

In plain words
What is it for?
Use it to search memory, read wiki pages, manage documents, and maintain connected notes about people, projects, events, and other entities.
Why use it?
It brings facts, files, and related notes together so information is easier to retrieve and connect later.

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/siddsachar/row-bot/knowledge_base
Any agent
npx skills add siddsachar/row-bot --skill knowledge_base
Clone the repo
git clone --depth 1 https://github.com/siddsachar/row-bot

Made for: Claude Code, Codex.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 687 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.00019 $0.00687
Opus 5 $0.00010 $0.00344
Sonnet 5 $0.00004 $0.00137
Haiku 4.5 $0.00002 $0.00069

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

Security

Grade A, and why

knowledge_base 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.

bundled_skills/knowledge_base/SKILL.md · 84 lines

How it starts

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

You are managing the user's personal knowledge base — a unified system combining a knowledge graph (entities + relations) with an Obsidian-compatible wiki vault of interconnected markdown files.

Your Knowledge System

The user's knowledge exists in three layers that you manage together:

  1. Knowledge Graph — Entities (people, facts, preferences, events, places, projects) and typed relations stored in a searchable graph database.
  2. Document Store — Uploaded files (PDF, DOCX, TXT) chunked and vectorized for semantic retrieval.
  3. Wiki Vault — Auto-exported markdown files that mirror the knowledge graph. Each entity with sufficient content gets its own .md file with YAML frontmatter, [[wiki-links]] to related entities, and a connections section.

When to Use Wiki Tools

  • search_memory — Hybrid search across the knowledge graph (semantic + keyword
    • graph expansion). Use when the user asks "what do you know about X", "search my knowledge base for Y", or when you need broader context than auto-recall provides.
  • wiki_read — When you need the full wiki article for a specific entity, including its frontmatter, connections, and complete description.
  • wiki_rebuild — After bulk memory operations (importing many facts, cleaning up duplicates) to regenerate all markdown files and indexes.
  • wiki_export_conversation — When the user says "save this conversation", "export our chat", or "add this to my wiki".
  • wiki_stats — When the user asks about the state of their knowledge base.

Building a Rich Knowledge Base

When the user shares information:

  1. Save the entity with save_memory (appropriate category, descriptive content)
  2. Link related entities with link_memories (use specific relation types)
  3. The wiki vault updates automatically — no extra step needed

Best Practices

  • Prefer specific relation types: mother_of over related_to
  • Add aliases when entities have multiple names: "Mom, Sarah, Mother"
  • Use tags for cross-cutting themes: "family,birthday,march"
  • Rich descriptions export as better wiki articles
  • When the user mentions Obsidian, explain that the vault syncs automatically and they can open it in Obsidian to see backlinks, graph view, and search

Read the full file on GitHub · 84 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 · 84 lines · 19 tokens per session scan A 6101986a3309

Subscribe to this mod's changes

knowledge_base is a skill published in the GitHub repository siddsachar/row-bot (1,479 stars, last pushed 4d ago), licensed Apache-2.0. It adds 19 tokens to every session and 687 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

rich-post

Send a Telegram rich-media post to ANOTHER allowlisted chat via the bot (Bot API 10.1 sendRichMessage) - text, inline images, tables, headings, lists, quotes, collapsible blocks, formulas, collages/slideshows ALL in one message bubble. Use when the owner asks to post somewhere other than the current conversation (the…

smixs/iva-agent · 129 tokens

telegram-userbot

Подключение и работа с личным Telegram-аккаунтом владельца (userbot, НЕ бот). Используй, когда просят читать личные чаты/переписку/диалоги, искать по своим сообщениям, писать кому-то от своего имени, «зайди в мой телеграм», «подключи мой телеграм», «прочитай личку», «ответь в личке», «перешли сообщение», а также при…

smixs/iva-agent · 144 tokens

memory-processor

Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…

smixs/iva-agent · 106 tokens

agent-browser

Браузерная автоматизация для интерактивных веб-задач. Используй, когда нужно открыть сайт, заполнить форму, кликнуть, сделать скриншот, залогиниться, спарсить JS-страницу или протестировать веб-приложение. Триггеры — «зайди на сайт», «заполни форму», «нажми кнопку», «скриншот страницы», «войди в аккаунт», «спарси…

smixs/iva-agent · 114 tokens

update-recovery

Restore or merge user customizations preserved during an Iva update. Use when the owner says "restore my update changes", "recover my customizations", «верни мои изменения после обновления», «восстанови мои доработки» or asks about an update conflict.

smixs/iva-agent · 60 tokens

security-defense

Procedures for handling untrusted content, suspected prompt injection, secret exposure, data exfiltration, and manual security inspection. Use for emails, web pages, forwarded messages, webhooks, group content, or a suspected leak. Do not use as a general claim that every command or model call is automatically…

smixs/iva-agent · 68 tokens