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 agentmods add skills/0xranx/golembot/kb-guidenpx skills add 0xranx/golembot --skill kb-guidegit clone --depth 1 https://github.com/0xranx/golembotWrote 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/0xranx/golembot/kb-guide)<a href="https://agentmods.dev/skills/0xranx/golembot/kb-guide"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/kb-guide.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.00066 | $0.00542 |
| Opus 5 | $0.00033 | $0.00271 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
kb-guide 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base Integration Guide
When MCP knowledge base servers are configured, you can use their tools to search, read, create, and update knowledge entries.
Common MCP Knowledge Base Tools
MCP KB servers typically expose tools with these patterns:
Search / Query
search_documents(query, limit?)-- full-text search across the knowledge basesearch_notes(query)-- search personal notes or wiki entriesquery_knowledge(query, filters?)-- filtered search with metadata constraints
Read
get_document(id)-- retrieve a document by IDread_page(path)-- read a wiki page by pathlist_documents(folder?, tag?)-- list documents in a folder or by tag
Create / Update
create_document(title, content, metadata?)-- create a new entryupdate_document(id, content)-- update an existing documentcreate_note(title, body)-- create a quick note
Example Tool Call
When a user asks "do we have docs on deployment?", search the KB first:
Tool: search_documents
Arguments: { "query": "deployment", "limit": 5 }
Present matching results with titles and snippets. If no results are found, offer to create a new entry.
When to Use Knowledge Base
- Before answering domain questions: Search the KB first -- it may contain authoritative answers
- When the user asks "do we have docs on...": Search the KB and return results
- After resolving an issue: Suggest creating a KB entry to capture the solution
- For onboarding/FAQ questions: Check if there's an existing KB article
Usage Pattern
- Identify the user's intent (search, read, write)
- Call the appropriate MCP tool by name
- If a tool is not available, inform the user that no KB server is configured
- Present results clearly -- include titles, snippets, and links when available
Notes
- MCP server configuration is defined in
golem.yamlunder themcpkey - Available MCP tools depend on which servers are configured -- use tool discovery to check
- Always prefer searching the KB before generating answers from your own training data
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.
- 6d ago First seen · 59 lines · 66 tokens per session scan A 8d55557312e3
kb-guide is a skill published in the GitHub repository 0xranx/golembot (320 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 542 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
project-memory-keeper
Analyzes the last session to log progress, extract lessons learned, and save them to the project memory instructions.
remember
Contemplates repeated mistakes and success patterns, and transforms lessons learned into domain-organized Copilot instructions. Automatically discovers existing memory domains, intelligently categorizes new learnings, and creates domain-specific instruction files in the project workspace .github/instructions/ folder.…
memory-manager
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
supamem
Project-agnostic dual-memory tooling — semantic + structural memory for AI coding agents.
memory
管理会话记忆的读取与写入。三层记忆体系：Agent 日记 / 需求记忆 / 项目总记忆。.
summary
写入会话摘要到记忆日文件。区别于 memory Skill（会话记录读写）。任务结束前与 memory Skill 配合完成记忆持久化。.