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 willynikes2/knowledge-base-server --skill skillgit clone --depth 1 https://github.com/willynikes2/knowledge-base-serverWrote 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/willynikes2/knowledge-base-server/skill)<a href="https://agentmods.dev/skills/willynikes2/knowledge-base-server/skill"><img src="https://agentmods.dev/badge/skills/willynikes2/knowledge-base-server/skill/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/willynikes2/knowledge-base-server/skill"><img src="https://agentmods.dev/badge/skills/willynikes2/knowledge-base-server/skill.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.00040 | $0.01071 |
| Opus 5.5 | $0.00016 | $0.00428 |
| Sonnet 5.5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
kb-workflow 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base Workflow
What This Skill Does
This skill teaches you how to use the knowledge-base-server MCP tools efficiently. It does NOT replace the MCP server — it complements it by giving you the retrieval strategy that saves 90%+ tokens.
Think of it this way:
- MCP server = the engine (search, read, write, capture)
- This skill = the driving instructions (when to search, what to read, how to capture)
Before Starting Any Task
Search the KB for relevant context BEFORE writing code or making decisions:
1. kb_context("topic") — get summaries only (~100 tokens per doc, 90% savings)
2. Review titles and summaries — decide which docs matter
3. kb_read(id) — read full content ONLY for docs you actually need
Never skip this. The KB has accumulated lessons, fixes, decisions, and architecture docs. Searching first prevents:
- Repeating solved problems
- Contradicting past decisions
- Missing known pitfalls
- Wasting tokens on re-discovery
The Three-Tier Retrieval Pattern
The KB has three tiers of information. Query the right tier for your need:
| Need | Tool | Tokens | When |
|---|---|---|---|
| Quick context | kb_context |
~100/doc | Always start here |
| Specific search | kb_search |
~200/result | Looking for something specific |
| Conceptual match | kb_search_smart |
~200/result | Fuzzy/semantic queries |
| Full document | kb_read |
~500-5000/doc | Only after context confirms relevance |
Rule: Never kb_read without kb_context first. You wouldn't read an entire book to check if it's relevant — you'd read the summary.
After Completing Work
Capture what you learned so the next session starts smarter:
After debugging sessions:
kb_capture_session:
goal: "What you were trying to do"
commands_worked: "What worked"
commands_failed: "What failed and why"
root_causes: "The actual problem"
fixes: "What fixed it"
lessons: "What to do differently next time"
After bug fixes:
kb_capture_fix:
title: "Short fix title"
symptom: "What was broken"
cause: "Root cause"
resolution: "How it was fixed"
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 · 122 lines · 40 tokens per session scan A 0dda59f2c613
kb-workflow is a skill published in the GitHub repository willynikes2/knowledge-base-server (189 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 1,071 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-08-30.
Other skills, from other repositories
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
memory-management
Two-tier memory that makes the agent a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so the agent understands requests like a colleague would. A small personal working-memory file for the hot cache, and the team's Hexis knowledge base (Glossary, People, Projects, How we…
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
productivity-update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
productivity-start
Initialize the productivity system - a task list and workplace memory. Use when setting up for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.
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.