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 samber/ccnpx agentmods add plugins/samber/cc/marketplacegit clone --depth 1 https://github.com/samber/ccGrade A, and why
samber 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "samber",
"owner": {
"name": "Samuel Berthe",
"email": "[email protected]"
},
"plugins": [
{
"name": "cc-caffeine",
"description": "Prevents your computer from sleeping while Claude Code works hard",
"source": {
"source": "github",
"repo": "samber/cc-caffeine"
},
"author": {
"name": "Samuel Berthe",
"email": "[email protected]"
},
"homepage": "https://github.com/samber/cc-caffeine",
"repository": "https://github.com/samber/cc-caffeine",
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-plugin",
"plugin",
"nap",
"sleep",
"sleep-prevention",
"caffeine",
"caffeinate",
"system-tray"
],
"category": "productivity"
},
{
"name": "cc-skills",
"description": "AI Agent Skills",
"source": {
"source": "github",
"repo": "samber/cc-skills"
},
"author": {
"name": "Samuel Berthe",
"email": "[email protected]"
},
"homepage": "https://github.com/samber/cc-skills",
"repository": "https://github.com/samber/cc-skills",
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-plugin",
"plugin",
"ai-agent",
"skills"
],
"category": "productivity"
},
{
"name": "cc-skills-golang",
"description": "AI Agent Skills for production-ready Go projects",
"source": {
"source": "github",
"repo": "samber/cc-skills-golang"
},
"author": {
"name": "Samuel Berthe",
"email": "[email protected]"
},
"homepage": "https://github.com/samber/cc-skills-golang",
"repository": "https://github.com/samber/cc-skills-golang",
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-plugin",
"plugin",
"golang",
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 · 112 lines scan A f827cdbcd090
samber is a plugin published in the GitHub repository samber/cc (5 stars, last pushed 2mo 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
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
OpenOutreach
The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.
skills
A curated collection of reliable workflows for AI agents.
lastlight
Install, configure and operate Last Light (GitHub maintenance agent) — its server, CLI client, deployment overlay, and the Last Light Evals harness.
junior-flow
Helps junior developers create technical story markdown from a story tracker.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…