claude-security

A Claude Code plugin for scanning your own code for security weaknesses and reviewing the results before reporting them.

In plain words
What is it for?
Use it to scan a repository for vulnerabilities, review challenged findings, and apply targeted security fixes after verification.
Why use it?
It helps separate likely vulnerabilities from findings that do not hold up, then prepares patches for issues you choose to fix. The checks and patches run within the Claude Code session.

Plugin for Claude Code

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.

agentmods
npx agentmods add plugins/anthropics/claude-plugins-official/claude-security
Claude Code
/plugin marketplace add anthropics/claude-plugins-official
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-plugins-official

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/claude-security/.claude-plugin/plugin.json · 21 lines

What it actually says

{
  "name": "claude-security",
  "version": "0.10.2.3",
  "description": "Deep vulnerability scanning of your own code, run entirely inside your Claude Code session at a chosen effort tier, with every finding challenged before it is reported and the verification tally computed in code. Turns surviving findings into targeted patches, each verified by a panel of agents, that you apply when you choose. See the plugin README for the tiers, the report format, and the trust model.",
  "author": {
    "name": "Anthropic",
    "email": "[email protected]"
  },
  "license": "SEE LICENSE IN LICENSE",
  "keywords": [
    "security",
    "vulnerability",
    "scan",
    "audit",
    "appsec",
    "code-review",
    "remediation",
    "autofix"
  ]
}
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.

  1. yesterday First seen · 21 lines scan A 0536c9089d4e

Subscribe to this mod's changes

claude-security is a plugin published in the GitHub repository anthropics/claude-plugins-official (35,577 stars, last pushed 3d ago), licensed Apache-2.0. 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-30.