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 ankushdixit/claude-pluginsnpx agentmods add plugins/ankushdixit/claude-plugins/marketplacegit clone --depth 1 https://github.com/ankushdixit/claude-pluginsGrade A, and why
claude-plugins 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 2d 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": "claude-plugins",
"owner": {
"name": "Ankush Dixit",
"email": "[email protected]"
},
"metadata": {
"description": "Official marketplace for Claude Code plugins",
"version": "1.0.0",
"pluginRoot": "."
},
"plugins": [
{
"name": "solokit",
"source": "./solokit",
"description": "Solokit - Structured Solo Development with AI and Quality Automation for Claude Code. Build production software alone with team-level sophistication.",
"version": "0.3.0",
"author": {
"name": "Ankush Dixit",
"url": "https://github.com/ankushdixit"
},
"homepage": "https://github.com/ankushdixit/solokit",
"repository": "https://github.com/ankushdixit/solokit",
"license": "MIT",
"keywords": [
"solo-development",
"ai-native",
"quality-automation",
"workflow",
"ai-development",
"claude-code",
"solokit"
],
"category": "productivity",
"tags": ["solo", "quality", "workflow", "productivity"]
}
]
}
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.
- 2d ago First seen · 39 lines scan A 2344fbb1ade3
claude-plugins is a plugin published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 7mo 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
humanizer
Rewrite AI-sounding text so it reads naturally 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.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.