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/fmind/agent-docsWrote 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/fmind/agent-docs/gemini-extension)<a href="https://agentmods.dev/plugins/fmind/agent-docs/gemini-extension"><img src="https://agentmods.dev/badge/plugins/fmind/agent-docs/gemini-extension/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/fmind/agent-docs/gemini-extension"><img src="https://agentmods.dev/badge/plugins/fmind/agent-docs/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-docs 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 3d 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": "agent-docs",
"version": "1.2.0",
"description": "Project docs that answer locally before the web — Agent Skills for AI coding agents."
}
What ships with it
5 files beside gemini-extension.json 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.
- 3d ago First seen · 6 lines scan A f34a2c1f9866
agent-docs is a plugin published in the GitHub repository fmind/agent-docs (3 stars, last pushed 3d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.
Other plugins, from other repositories
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and thirty-eight more — searchable and recalled, including work from before it was installed.
coder-eval
Test whether your Claude Code skills actually trigger, and benchmark any coding agent — author, run, and analyze the eval suite that proves it, locally or as a CI gate.
deslop marketplace
Claude Code distribution for the deslop Agent Skill.
playcanvas
Skills for building applications with PlayCanvas Engine.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
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…