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/bearlike/AssistantWrote 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/bearlike/assistant/unknown)<a href="https://agentmods.dev/plugins/bearlike/assistant/unknown"><img src="https://agentmods.dev/badge/plugins/bearlike/assistant/unknown/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/bearlike/assistant/unknown"><img src="https://agentmods.dev/badge/plugins/bearlike/assistant/unknown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-review 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.
This is a copy
86% identical to code-review — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "code-review",
"description": "Automated code review for pull requests using multiple specialized agents with confidence-based scoring"
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 5 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 5 lines scan A 47985d8f0f70
code-review is a plugin published in the GitHub repository bearlike/Assistant (44 stars, last pushed 2d ago), licensed MIT. 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. It is 86% identical to code-review, differing in 7 lines, and is treated as a copy.
Other plugins, from other repositories
webfetch
Own your LLM's web search: websearch, fetchurl, and savefinding tools backed by a local search -> fetch -> rank pipeline with semantic caching - up to 8x fewer input tokens and 3x lower cost than hosted web search.
code-review
Code review plugin.
diffctx
Selects the minimum code an LLM needs to review a git diff.
code-quality
Code quality pipeline — SOLID refactoring, TDD workflow, design patterns, performance optimization, and 6 specialist review agents.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.