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.
git 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/plugins/freepeak/leankg/gemini-extension)<a href="https://agentmods.dev/plugins/freepeak/leankg/gemini-extension"><img src="https://agentmods.dev/badge/plugins/freepeak/leankg/gemini-extension.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
leankg 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 yesterday.
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
{
"name": "leankg",
"description": "Lightweight knowledge graph for AI-assisted development. Impact analysis, code search, dependency tracking, and context generation.",
"version": "0.1.0",
"contextFileName": "GEMINI.md"
}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.
- yesterday First seen · 6 lines scan A fb1d96ec5181
leankg is a plugin published in the GitHub repository FreePeak/LeanKG (216 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-06.
Other plugins, from other repositories
potpie
Project-memory context engine for Claude Code: surfaces preferences, prior bugs/fixes, infra topology, timeline context, and durable-capture prompts. Hooks are model-free; the in-session harness decides what is true and writes semantic graph mutations.
memora
Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools for memory management.
engraphis-memory
Give agents durable, scoped, explainable memory across sessions and repos via the Engraphis MCP tools. Use when you learn something worth keeping, need prior context before acting, or ask why/how a fact changed. Covers remember/recall, why/timeline, forget/pin/correct, sessions, and code search.
kin
Kin keeps a living map of the software itself so humans and agents can understand what every change touches. Locate, search, context packs, data-flow tracing, and impact analysis without raw file search.
umodel
Use UModel from your agent: read entities, relationships, topology, and the model itself; discover and follow entity-linked RunbookSet Skills; and run model-guided root-cause analysis. Bundles three UModel skills.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…