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/antonbabenko/agent-pluginsWrote 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/antonbabenko/agent-plugins/code-intelligence)<a href="https://agentmods.dev/plugins/antonbabenko/agent-plugins/code-intelligence"><img src="https://agentmods.dev/badge/plugins/antonbabenko/agent-plugins/code-intelligence/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/plugins/antonbabenko/agent-plugins/code-intelligence"><img src="https://agentmods.dev/badge/plugins/antonbabenko/agent-plugins/code-intelligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-intelligence 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 1mo 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
{
"name": "code-intelligence",
"source": "./plugins/code-intelligence",
"description": "Use when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.",
"category": "development",
"keywords": [
"lsp",
"code-intelligence",
"code-navigation",
"language-server",
"refactoring",
"search-precedence",
"tool-disclosure"
],
"version": "0.5.0"
}What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 78 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#code-intelligence in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 16 lines scan A 601fc1d332c5
code-intelligence is a plugin published in the GitHub repository antonbabenko/agent-plugins (46 stars, last pushed 5d ago), 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-03.
Other plugins, from other repositories
development
Development — The craft that is independent of language: review, debugging, refactoring, design, and version control.
complexity-reducer
Reduce cyclomatic complexity and simplify functions.
double-check
Verify code correctness with systematic second-pass analysis.
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.
code-review-assistant
Automated code review with severity levels and actionable feedback.
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…