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/josix/agent-flow/personal-kb-usagenpx skills add josix/agent-flow --skill personal-kb-usagegit clone --depth 1 https://github.com/josix/agent-flowWrote 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/josix/agent-flow/personal-kb-usage)<a href="https://agentmods.dev/skills/josix/agent-flow/personal-kb-usage"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/personal-kb-usage.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 | $0.00039 | $0.01856 |
| Opus 5 | $0.00019 | $0.00928 |
| Sonnet 5 | $0.00008 | $0.00371 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
personal-kb-usage 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 4d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal KB Usage
Query the user's personal knowledge base effectively, interpret results accurately, and stay within token budgets.
Overview
The personal-kb MCP server exposes the user's cross-project personal knowledge base as a pre-built knowledge graph stored at $AGENT_FLOW_PERSONAL_KB_PATH/graphify-out/graph.json. This is a graph built by the user from their own notes, journals, decision records, or any other personal documents — outside of any single project directory.
Owner: Riko (Explorer Agent) — Riko is the primary personal-kb query agent and owns interpretation of results. Consumers: Senku (Planner Agent), Lawliet (Reviewer Agent) — both may consult the personal KB during planning and review to surface cross-project decisions and patterns. Out of scope: Loid (Executor) and Alphonse (Verifier) do NOT have personal-kb access by design. This preserves the one-writer invariant and keeps write/verify agents focused on project artifacts.
All 7 tools are accessed via the MCP prefix mcp__personal-kb__*. See references/tool-reference.md for full signatures.
Contrast with graphify-usage:
graphify-usage— queries the current project's graph atgraphify-out/graph.json(relative to project root). Use for structural questions about THIS codebase.personal-kb-usage— queries the user's personal graph at an absolute path outside the project. Use for cross-project recall: prior decisions, anti-patterns encountered before, personal preferences, notes from past work.
When to Query the Personal KB vs. Project Graph vs. Grep
| Trigger condition | Preferred approach |
|---|---|
| "Have I solved this problem before in another project?" | Personal KB: query_graph |
| "What did I decide about X in past projects?" | Personal KB: query_graph |
| "What patterns have I used for Y across codebases?" | Personal KB: query_graph |
| "What personal anti-patterns have I documented?" | Personal KB: god_nodes then get_community |
| "What is the dependency structure of THIS project?" | Project graph (graphify-usage) |
| "Which community does file F belong to in THIS repo?" | Project graph (graphify-usage) |
"Find the string literal TODO: fix" |
Grep |
| "What does a specific config key say in THIS project?" | Read the file directly |
Personal KB is not configured (available: false in state) |
Skip — use project graph or Grep |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 135 lines · 39 tokens per session scan A 2e5cf5b15f8e
personal-kb-usage is a skill published in the GitHub repository josix/agent-flow (7 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 1,856 once invoked, about $0.0002 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-31.
Other skills, from other repositories
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
memory-and-context
Store, retrieve, search, and manage persistent memory across sessions. Triggers on: store memory, save this, retrieve, forget, manage memory, context, pattern.
recall
Pull relevant findings stashed from past sessions — on demand. Triggers on: recall, remember, what did I learn, prior session, past findings, did I hit this before, what do we know about.
personal-memory
Capture and recall curated cross-session personal memory — decisions, preferences, findings by topic. Triggers on: remember this for me, capture this decision, save to personal memory, my saved topics, forget topic, personal memory.
help
Skill "help" from Smart-AI-Memory/attune-ai, covering help and behavior.
codebase-memory-mcp
Optimizes local code intelligence and discovery using a high-performance, Tree-sitter-backed structural knowledge graph instead of expensive token-heavy file searches. Use for understanding code architecture, tracing function call chains, finding cross-file dependencies, analyzing git diff blast radiuses, running…