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 instructions/fulminate-io/knowledge-mcp/claude-mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/instructions/fulminate-io/knowledge-mcp/claude-md)<a href="https://agentmods.dev/instructions/fulminate-io/knowledge-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/fulminate-io/knowledge-mcp/claude-md.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.03209 | $0.03209 |
| Opus 5 | $0.01605 | $0.01605 |
| Sonnet 5 | $0.00642 | $0.00642 |
| Haiku 4.5 | $0.00321 | $0.00321 |
Grade A, and why
knowledge-mcp CLAUDE.md 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 5d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge
A persistent memory and reasoning graph for LLMs. Runs as a local MCP server. Primitives: think / charge / recall for hypothesis + evidence, informed-by edges linking code → decision → plan, triple-graph architecture (code + cloud + knowledge). Free OSS; Fulminate Cloud hosts the paid tiers.
Build
CGO_ENABLED=1 go build -o bin/knowledge . # MCP stdio client
CGO_ENABLED=1 go test -p 4 ./... # all tests
CGO is required for tree-sitter C bindings (31 language grammars).
Setup
The knowledge binary is the MCP stdio client. It needs a graph server to talk to. Two options:
Local server (free, file-backed):
knowledge install # downloads the server binary for your platform
knowledge start # spawns the server on 127.0.0.1:15022
knowledge status # confirm running
Fulminate Cloud (paid, team-shared):
knowledge login # browser-PKCE OAuth flow
Once a server is available, point your MCP host at the client:
{
"mcpServers": {
"knowledge": {
"command": "knowledge",
"args": ["--root", "."]
}
}
}
The stdio client auto-connects to 127.0.0.1:15022 when unauthenticated, or routes to Fulminate Cloud when logged in. Run knowledge login for paid cloud features (team sync, always-on agents). Browser-only by design — headless environments are not supported.
Code Exploration: knowledge tools FIRST, shell tools LAST
Default to search, file_symbols, and traverse for every code-exploration task. Grep / Glob / Read / Bash-tail are the fallback, not the starting point. The knowledge graph is indexed, semantically aware, and knows the call graph — shell tools aren't. Reaching for grep first is almost always slower and less accurate.
| Want to... | Use this first | Not this |
|---|---|---|
| Find functions, types, patterns, implementations | search({ "queries": [...] }) (batch 3-5 terms) |
Grep / rg |
| List symbols in a file before editing | file_symbols({ "file_path": "..." }) |
Read the whole file |
| Find callers of a function | traverse({ "start": "path/to/file.go:Func", "graph": "code", "repo": "...", "edge_types": ["CALLS"], "direction": "in" }) |
grep -rn 'FuncName(' |
| Find callees of a function | traverse({ "start": "path/to/file.go:Func", "graph": "code", "repo": "...", "edge_types": ["CALLS"], "direction": "out" }) |
grep -rn 'FuncName(' |
Find structural patterns (every defer X.Close(), every sync.Once.Do, every error-returning func decl) |
ast({ "operation": "match", "language": "go", "pattern": "defer $X.Close()" }) |
grep (misses through whitespace, comments, token reorder) |
| Apply a UNIFORM structural edit across many files (rename a call pattern, wrap/unwrap a call, swap a deprecated API) | ast({ "operation": "replace", "language": "go", "pattern": "defer $X.Close()", "replacement": "defer safeClose($X)" }) — dry-run previews the diff (default), dry_run:false applies |
sed / perl -pi / grep+script (mangle multi-line + slice literals, can't scope by enclosing type, no re-parse safety) |
| Search knowledge (decisions, findings, rules, past thoughts) | search({ "queries": [...], "graph": "knowledge" }) or recall({ "text": "..." }) |
Reading docs manually |
| Inspect a node's full context (ancestry, edges, history) | query({ "mode": "examine", "id": "..." }) |
Multiple individual queries |
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.
- 5d ago First seen · 168 lines · 3,209 tokens per session scan A d90b0761d905
knowledge-mcp CLAUDE.md is an instructions file published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,209 tokens to every session, about $0.0160 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 instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.