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 ChamHerry/claude-code-third-party-pluginsnpx agentmods add plugins/chamherry/claude-code-third-party-plugins/marketplacegit clone --depth 1 https://github.com/ChamHerry/claude-code-third-party-pluginsGrade A, and why
claude-code-third-party-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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "claude-code-third-party-plugins",
"version": "1.0.0",
"description": "Claude Code 插件市场，包含项目初始化、开发辅助等实用工具",
"owner": {
"name": "Wang Xuecheng",
"email": "[email protected]"
},
"plugins": [
{
"name": "project-init",
"description": "基于 CLAUDE_TEMPLATE.md 模板快速初始化项目 CLAUDE.md 规范文件，通过交互式问答生成定制化开发规范",
"version": "1.0.0",
"author": {
"name": "Wang Xuecheng",
"email": "[email protected]"
},
"source": "./plugins/project-init",
"category": "productivity"
},
{
"name": "session-manager",
"description": "智能保存和恢复 Claude Code 会话，支持进度跟踪、决策记录和工作连续性，采用项目本地存储和智能数据访问设计",
"version": "1.0.0",
"author": {
"name": "Wang Xuecheng",
"email": "[email protected]"
},
"source": "./plugins/session-manager",
"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.
- 2d ago First seen · 35 lines scan A ac7920fdee99
claude-code-third-party-plugins is a plugin published in the GitHub repository ChamHerry/claude-code-third-party-plugins (50 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-30.
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.