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 lhohan/claude-code-pluginsnpx agentmods add plugins/lhohan/claude-code-plugins/marketplacegit clone --depth 1 https://github.com/lhohan/claude-code-pluginsGrade A, and why
hanlho-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 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
{
"name": "hanlho-plugins",
"owner": {
"name": "Hans L'Hoest",
"email": "[email protected]"
},
"metadata": {
"description": "Hanlho's collection of reusable plugins for Claude Code to enhance your development workflow. Geared towards architecture and code quality.",
"version": "1.0.0",
"repository": {
"type": "git",
"url": "https://github.com/lhohan/claude-code-plugins"
}
},
"plugins": [
{
"name": "jujutsu-vcs",
"source": "./jujutsu-vcs",
"description": "SessionStart hook that ensures Claude Code uses Jujutsu (jj) commands instead of git in Jujutsu repositories",
"version": "1.0.0",
"keywords": ["jujutsu", "vcs", "version-control", "jj"],
"category": "version-control"
},
{
"name": "skill-evaluator",
"source": "./skill-evaluator",
"description": "Evaluate Claude Code skills against best practices including size, structure, examples, and prompt engineering quality. Provides comprehensive analysis with actionable suggestions.",
"version": "0.1.0",
"keywords": ["skill", "evaluation", "quality-assurance", "best-practices", "code-review"],
"category": "development"
},
{
"name": "hanlho-cmds",
"source": "./hanlho-cmds",
"description": "Curated most useful & frequently used Claude Code commands for Claude development and workflow automation",
"version": "0.1.0",
"keywords": ["productivity", "workflow", "automation", "development", "commands"],
"category": "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.
- yesterday First seen · 42 lines scan A 3934a1c56b15
hanlho-plugins is a plugin published in the GitHub repository lhohan/claude-code-plugins (2 stars, last pushed 9mo 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
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.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.