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.
/plugin marketplace add fmind/agent-docsnpx agentmods add plugins/fmind/agent-docs/marketplacegit clone --depth 1 https://github.com/fmind/agent-docsGrade 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 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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "agent-docs",
"description": "Project docs that answer locally before the web — Agent Skills for AI coding agents.",
"owner": {
"name": "Médéric Hurier",
"email": "[email protected]"
},
"plugins": [
{
"name": "agent-docs",
"source": "./",
"description": "Project docs that answer locally before the web — Agent Skills for AI coding agents.",
"author": {
"name": "Médéric Hurier",
"email": "[email protected]",
"url": "https://fmind.dev"
},
"homepage": "https://github.com/fmind/agent-docs",
"repository": "https://github.com/fmind/agent-docs",
"license": "MIT",
"keywords": [
"agentic-coding",
"agent-skills",
"documentation",
"agent-docs",
"gemini-cli",
"claude-code",
"github-copilot",
"opencode"
],
"category": "documentation"
}
]
}
What ships with it
1 file beside marketplace.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.
- yesterday First seen · 36 lines scan A 6b89db6f7cec
agent-docs is a plugin published in the GitHub repository fmind/agent-docs (3 stars, last pushed 3mo 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-08-31.
Other plugins, from other repositories
concord-relay
Delivers Concord inter-agent messages into a running Claude Code session, whether it is mid-task or idle at the prompt.
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
Claude Code distribution for the deslop Agent Skill.
infino-ai
Plugin marketplace listing 1 plugin: code-context.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
development
Code development and quality assurance tools - analyze, test, fix, review.