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.
git clone --depth 1 https://github.com/terrylica/cc-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/terrylica/cc-skills/plugin-dev)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/plugin-dev"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/plugin-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
plugin-dev 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": "plugin-dev",
"description": "Plugin and skill development: structure validation, silent failure auditing, skill architecture meta-skill with TodoWrite templates",
"version": "30.1.0",
"source": "./plugins/plugin-dev",
"category": "development",
"author": {
"name": "Terry Li",
"url": "https://github.com/terrylica"
},
"keywords": [
"plugin",
"skill",
"validation",
"silent-failures",
"meta-skill",
"skill-creation",
"architecture",
"templates",
"shellcheck"
],
"strict": false
}What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 87 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
3 files beside marketplace.json#plugin-dev 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.
- 2d ago First seen · 23 lines scan A 651ebc77e0c0
plugin-dev is a plugin published in the GitHub repository terrylica/cc-skills (62 stars, last pushed yesterday), 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-09-05.
Other plugins, from other repositories
infra-standards
Infrastructure standards for Proxmox, Terraform, Ansible: VMID/IP assignment ranges and the Terraform-to-Ansible inventory contract.
LUXOR DevOps Suite
Complete DevOps and infrastructure skills covering Docker, Kubernetes, AWS, Terraform, CI/CD, monitoring, microservices, and API gateways.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.