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 ondrasek/cc-pluginsnpx agentmods add plugins/ondrasek/cc-plugins/marketplacegit clone --depth 1 https://github.com/ondrasek/cc-pluginsGrade A, and why
cc-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": "cc-plugins",
"owner": {
"name": "ondrasek"
},
"plugins": [
{
"name": "blueprint",
"source": "./plugins/blueprint",
"description": "Quality methodology for Python, .NET, Rust, and Neovim Lua projects"
},
{
"name": "github-issues",
"source": "./plugins/github-issues",
"description": "Intelligent GitHub issue management for Claude Code via gh CLI"
},
{
"name": "github-releases",
"source": "./plugins/github-releases",
"description": "Intelligent GitHub release management for Claude Code via gh CLI"
},
{
"name": "git-auto-commit",
"source": "./plugins/git-auto-commit",
"description": "Fail-fast cascade checker — enforces staging, conventional commits, and push via Stop hook"
},
{
"name": "auto-release",
"source": "./plugins/auto-release",
"description": "Automated semantic versioning and GitHub releases from conventional commits"
},
{
"name": "obsidian-blueprint",
"source": "./plugins/obsidian-blueprint",
"description": "Quality methodology for git-managed Obsidian vaults — 7 dimensions of content quality plus calendar integration"
},
{
"name": "calendar-access",
"source": "./plugins/calendar-access",
"description": "Read-only calendar access via CLI tools — Google Calendar (gcalcli) and Microsoft 365 (Azure CLI + Graph API)"
}
]
}
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 · 44 lines scan A f266260e3eb8
cc-plugins is a plugin published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. 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.