cblecker-claude-plugins

Install

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.

Security

Grade A, and why

cblecker-claude-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.

.claude-plugin/marketplace.json · 48 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-marketplace.json",
  "name": "cblecker-claude-plugins",
  "version": "1.0.0",
  "description": "Personal collection of Claude Code plugins",
  "owner": {
    "name": "Christoph Blecker",
    "email": "[email protected]"
  },
  "plugins": [
    {
      "name": "git",
      "source": "./git",
      "strict": true
    },
    {
      "name": "github",
      "source": "./github",
      "strict": true
    },
    {
      "name": "pr-review-toolkit",
      "source": "./pr-review-toolkit",
      "strict": true
    },
    {
      "name": "gws",
      "source": "./gws",
      "strict": true
    },
    {
      "name": "rh-dataverse",
      "source": "./rh-dataverse",
      "strict": true
    },
    {
      "name": "sandbox-ssh-fix",
      "source": "./sandbox-ssh-fix",
      "strict": true
    },
    {
      "name": "plan-review",
      "source": "./plan-review",
      "strict": true
    }
  ]
}

Changes

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.

Related

Other plugins, from other repositories