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 FreePeak/LeanKG --skill usagegit clone --depth 1 https://github.com/FreePeak/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/usage)<a href="https://agentmods.dev/skills/freepeak/leankg/usage"><img src="https://agentmods.dev/badge/skills/freepeak/leankg/usage/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/freepeak/leankg/usage"><img src="https://agentmods.dev/badge/skills/freepeak/leankg/usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00374 |
| Opus 5.5 | $0.00011 | $0.00150 |
| Sonnet 5.5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
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 2mo 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.
What it actually says
Use LeanKG tools to explore and understand code:
mcp_status- Check if LeanKG is initializedmcp_init- Initialize LeanKG for a project:mcp_init { path: "<project>/.leankg" }mcp_index- Index a directory:mcp_index { path: "<project>/src" }search_code- Find code elements:search_code { query: "<function_name>" }find_function- Locate a function:find_function { name: "<name>" }query_file- Find files:query_file { query: "<filename>" }get_impact_radius- Calculate blast radius:get_impact_radius { file: "<path>", depth: <n> }get_dependencies- Get imports:get_dependencies { file: "<path>" }get_dependents- Get dependents:get_dependents { file: "<path>" }get_context- Get file context:get_context { file: "<path>" }get_call_graph- Get call chains:get_call_graph { file: "<path>" }get_tested_by- Get test coverage:get_tested_by { file: "<path>" }
Rule: Use LeanKG first, before grep/ripgrep.
LeanKG auto-initializes on first use. If .leankg does not exist, it creates one automatically. If index is stale (>5 min since last git commit), it re-indexes automatically.
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.
- 2mo ago First seen · 23 lines · 27 tokens per session scan A c8061aae09c2
usage is a skill published in the GitHub repository FreePeak/LeanKG (222 stars, last pushed 8d ago), licensed Apache-2.0. It adds 27 tokens to every session and 374 once invoked, about $0.0001 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
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, resource (document payload) commands, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
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-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
ops-metrics-analysis
A guided procedure for analyzing 180 days of daily network-operations metrics from a CSV file. It compares service areas and checks connection rate, drop rate, latency, alerts, tickets, SLA performance, and satisfaction.
analyze-type-infer
A compiler analysis step that infers a symbol's type from its assignments. A type describes what kind of value something holds, such as a number, text, or Boolean value.