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 rube-de/cc-skillsnpx agentmods add plugins/rube-de/cc-skills/dlcgit clone --depth 1 https://github.com/rube-de/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/rube-de/cc-skills/dlc)<a href="https://agentmods.dev/plugins/rube-de/cc-skills/dlc"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/dlc.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dlc 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": "dlc",
"description": "Dev Life Cycle quality gates: security scans, code quality, performance analysis, test coverage, and PR review compliance with automated GitHub issue creation",
"version": "2.14.0",
"source": "./plugins/dlc",
"category": "quality",
"author": {
"name": "rube-de",
"url": "https://github.com/rube-de"
},
"keywords": [
"dev-lifecycle",
"security",
"quality",
"performance",
"testing",
"pr-review",
"pr-validity",
"git-ops",
"github-issues"
]
}What it installs
The manifest is a name and a version. 10 skills travel with it, and installing the plugin installs all of them — 448 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#dlc 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 Changed 36a9a900c27f
- 2d ago First seen · 22 lines scan A 6dd20bb90b4b
dlc is a plugin published in the GitHub repository rube-de/cc-skills (10 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-03.
Other plugins, from other repositories
agent-harness
Multi-agent harness for Claude Code: Planner→Generator→Evaluator sprints executed as background dynamic workflows (Agent-tool fallback), fable/opus/sonnet/haiku model routing with per-role reasoning effort, harness-engineering framework for design/diagnosis, and Anthropic 2026-04-04 P-G-E pattern.
hato
Carrier-pigeon messaging between Claude Code sessions — send messages and files, and get woken up by other sessions across your machines.
productionos
AI engineering OS for Claude Code and Codex — 80 agents, 41 commands, 18 hooks.
orodruin-labs marketplace
Plugin marketplace listing 1 plugin: nazgul.
mz
Unified framework for project management, code quality, and multi-agent coordination.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.