Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add FreePeak/LeanKG/plugin install leankgWrote 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/freepeak/leankg/using-leankg)<a href="https://agentmods.dev/skills/freepeak/leankg/using-leankg"><img src="https://agentmods.dev/badge/skills/freepeak/leankg/using-leankg.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.00043 | $0.01278 |
| Opus 5 | $0.00022 | $0.00639 |
| Sonnet 5 | $0.00009 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
using-leankg scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf --max-time 2 http://localhost:9699/health How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LeanKG Code Search (HTTP-gated)
LeanKG is preferred when the MCP HTTP server is up. If health fails, exit this skill immediately and use default Cursor/editor tools.
Gate (ALWAYS FIRST)
curl -sf --max-time 2 http://localhost:9699/health
| Result | Next step |
|---|---|
| Success (2xx) | Continue with LeanKG MCP below |
| Fail / timeout / connection refused | Exit skill. Use Grep, Glob, Read. Do not call LeanKG MCP, mcp_init, or leankg CLI |
Re-check health only if the user asks or you have reason to believe the server came back.
When HTTP is healthy: LeanKG MCP
Project path (Docker vs host)
When talking to Docker MCP on :9699, pass the container mount as project=:
| Target | project= |
|---|---|
| This LeanKG repo | /workspace |
| Extra bind (compose override) | /workspace-other (or the container side of the bind) |
Do not pass a Mac host path (e.g. /Users/.../leankg) as project against Docker RocksDB.
Prefer-order (discover → exact)
Session start (overview):
get_overview_context(project=…) # L0+L1 summary — not load_layer(L0) alone
→ optional load_layer for progressive budgets
→ get_architecture for deep single-call overview
Natural-language / domain questions (discover before query_graph):
1. mcp_status(project=…)
2. concept_search(query=…) # domain concepts first
3. semantic_search(query=…) # HNSW ANN if embeddings exist — REQUIRED before query_graph
4. search_code / find_function # name/type fallback
5. query_graph / explain_node / shortest_path # only after seeds / known endpoints
6. get_context / get_impact_radius / get_dependencies / …
on the returned qualified_name or file — never full-graph dumps
BAN: Do not call query_graph as the first NL discovery tool. Run concept_search → semantic_search first; use query_graph to expand the frontier after hits.
Exact symbol / file known:
mcp_status → find_function / query_file → get_context → impact/deps tools
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.
- 7d ago First seen · 132 lines · 43 tokens per session scan A 0b1b5c0d59c6
using-leankg is a skill published in the GitHub repository FreePeak/LeanKG (216 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,278 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
pr-comment-evaluator
Use to judge whether a PR review comment sounds polite.
diff-risk-explainer
Use to briefly explain small code diffs.
omnigraph
Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…
code-knowledge-graph
Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
raytsystem-run-review
Independently review an raytsystem run, diff, contract, test result, or milestone checkpoint and return structured findings. Use for REVIEW, architecture/contracts/data-integrity/test critique, gate verification, or pre-promotion review; remain read-only and separate from the writer context.