claude-code-kit

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

claude-code-kit 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 · 24 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "claude-code-kit",
  "description": "Turn any task into production-ready code. Specialized agents automatically handle planning, implementation, code review, and security scanning for any stack.",
  "owner": {
    "name": "This-HW",
    "url": "https://github.com/This-HW"
  },
  "repository": "https://github.com/This-HW/claude-code-kit",
  "plugins": [
    {
      "name": "claude-code-kit",
      "description": "Turn any task into production-ready code. Specialized agents automatically handle planning, implementation, code review, and security scanning for any stack.",
      "category": "development",
      "source": {
        "source": "git-subdir",
        "url": "https://github.com/This-HW/claude-code-kit",
        "path": "plugins/common"
      },
      "homepage": "https://github.com/This-HW/claude-code-kit"
    }
  ]
}

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