personal-kb-usagelisted

# 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](references/tool-reference.md) for full signatures. **Contrast with `graphify-usage`**: - `graphify-usage` — queries the **current project's** graph at `graphify-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-patter