Anthropic Releases Claude Security Plugin for Claude Code in Beta: A Multi-Agent Vulnerability Scanner That Runs in Your Terminal
Anthropic has launched the Claude Security plugin for Claude Code in beta. The plugin runs a multi-agent vulnerability scan of a repository from inside an present Claude Code session, then turns the findings you choose into patch recordsdata that you simply overview and apply your self. Anthropic emphasised the software’s versatility upon announcement, highlighting its functionality to both run a complete scan throughout the complete codebase or examine adjustments from the terminal proper earlier than a commit.
What plugin provides
The plugin provides a single command, /claude-security, which opens a menu of three jobs, per the official documentation:
- Scan codebase — the entire repository or a scoped subset of it
- Scan adjustments — a department’s diff, a pull request’s diff, or a single commit
- Suggest patches — flip a report’s findings into .patch recordsdata
Installation is 2 instructions from the official Anthropic marketplace:
/plugin set up claude-security@claude-plugins-official
/reload-plugins
If {the marketplace} is just not discovered, run /plugin market add anthropics/claude-plugins-official first. The plugin supply is public in the claude-plugins-official repository, presently at model 0.10.0.
How the scan pipeline is structured
The scan is applied as a dynamic workflow — a JavaScript orchestration script that followers work out throughout subagents. The script declares six phases:
- Inventory: partition the repository into parts. Every top-level listing have to be both scanned or explicitly skipped with a cause.
- Threat mannequin: one modeler per part, producing entry factors, sinks, belief boundaries, and recordsdata a researcher should learn in full.
- Research: one researcher per part × class cell.
- Sweep: gap-fill over what the matrix didn’t cowl.
- Panel: three-lens adversarial verification, one voter per lens.
- Adversarial: max effort solely: re-panel marginal retains, then red-team each survivor.
Research runs in opposition to 4 mounted classes: injection-and-input, auth-and-access, memory-and-unsafe, and crypto-and-secrets. The memory-and-unsafe lens is dropped for parts written completely in memory-safe languages, so a pure Python or TypeScript part will get three lenses as a substitute of 4.
The operational scale of a run is dictated by 4 distinct effort tiers: low, medium, excessive, and max. Depending on the chosen tier, particular thresholds are enforced: the utmost variety of parts is capped at 12 for low and medium tiers, increasing to 24 for excessive and max tiers; matrix cells are assigned 1 researcher, which will increase to 2 on the excessive and max ranges; and the variety of gap-fill sweeps scales from 0 at low, to 1 at medium, as much as 2 for excessive and max. When coping with a restricted scope or a small diff, the method condenses right into a single-researcher configuration as a substitute of deploying all the matrix. This ensures the analysis stays strictly proportionate to the goal whereas sustaining the an identical verification customary.
The system employs model-tiered brokers: the orchestrator runs on Opus, whereas the repository cartographer and read-only code explorer run on Sonnet. Furthermore, the session mannequin is inherited by researchers and verifiers, and scan brokers are restricted completely to read-only instruments.
How a discovering earns its place in the report
This is the half price understanding intently. A candidate discovering doesn’t go into the report as a result of a researcher discovered it. It goes in solely after surviving a panel.
Each candidate is handed to a few unbiased verifiers, one per lens: REACHABILITY, IMPACT, and DEFENSES. Each returns a structured verdict of TRUE_POSITIVE or FALSE_POSITIVE with one or two strains naming the decisive file:line. The preserve quorum is 2 of three. If fewer than three voters return, the candidate is just not keepable in any respect.
The panel end result additionally caps the discovering’s said confidence. A unanimous 3/3 panel permits a confidence ceiling of excessive; a 2/3 quorum caps it at medium. A discovering can’t declare extra confidence than its verification earned.
Critically, the tally is computed in Python by the report renderer, not asserted by the mannequin that produced the findings. The revision stamp’s verification.standing is ready to verified solely when the vote document proves the panel ran for each discovering in the report; in any other case it’s unverified with a said cause. That makes the report’s personal account of its rigor one thing you may test slightly than one thing you tackle belief.
What a scan writes to disk
Every scan writes a timestamped CLAUDE-SECURITY-<timestamp>/ listing into the repository containing three artifacts:
- CLAUDE-SECURITY-RESULTS.md — the human-readable report. Each discovering carries an ID reminiscent of F1, plus severity (HIGH/MEDIUM/LOW), confidence, CWE ID, the precise sink line, impression, exploit situation, preconditions, and a advice.
- CLAUDE-SECURITY-RESULTS.jsonl — the identical findings, one JSON object per line.
- CLAUDE-SECURITY-REVISION-<commit>.json — the revision stamp: which commit was scanned, at what effort, the severity counts, and the way totally the run was verified. The filename carries -dirty when uncommitted adjustments have been a part of the scanned tree.
That listing is the one change a scan makes to your checkout, and it ships with its personal .gitignore so a stray git add can’t sweep a report right into a commit. Deleting that one .gitignore allows you to commit the report for an audit path.
Patches, and the three claims each should earn
The repair job develops every patch in a scratch clone of the repository, so your working tree and index are by no means touched. An agent unbiased of the one which wrote the patch then opinions the staged diff and runs the undertaking’s personal check suite in opposition to the change.
A patch file is written provided that the verifier can state all three of those with confidence: the change addresses that one discovering, it introduces no new vulnerability, and conduct is in any other case unchanged — the place a change to which inputs the code accepts counts as a conduct change. Any change that weakens safety whereas claiming to repair it, reminiscent of a loosened auth test or a disabled check, is an computerized reject. When the verifier can’t vouch for all three, you get a brief observe explaining why as a substitute of a patch.
Patches land in the report’s patches/ folder as F<n>.patch. Nothing is utilized routinely:
git apply CLAUDE-SECURITY-<timestamp>/patches/F1.patch
The patch observe explicitly signifies if no repository check covers the modified code, clarifying that the verification depends on code overview slightly than check execution. Anthropic suggests that every patch ought to be utilized utilizing a person pull request.
Requirements, price, and the belief mannequin
The plugin requires a paid plan with Claude Code v2.1.154 or later, with dynamic workflows enabled in /config. It additionally wants Python 3.9.6 or later in your PATH as python3 (utilizing solely the usual library) and Git for change scans and patching. Linux, macOS, and Windows are supported, and scans depend in opposition to your plan’s token limits.
Running in your session beneath your permissions, the scan provides no isolation of its personal, that means dedicated .claude/ settings, hooks, and CLAUDE.md nonetheless apply. While it treats repository content material as information slightly than directions, this isn’t a protection in opposition to hostile repositories; use sandbox-runtime to sandbox unfamiliar codebases.
Additionally, scans are nondeterministic and don’t change conventional static evaluation, dependency scanning, or code opinions.
Where it sits in the stack
| Stage | Tool | What it covers |
|---|---|---|
| In session | Security guidance plugin | Common vulnerabilities in code Claude writes, mounted in the identical session |
| On demand, single move | /security-review | One-time safety move on the present department |
| On demand, deep scan | Claude Security plugin | Multi-agent scan of a repository or diff, independently reviewed findings and patches |
| On pull request | Code Review (Team, Enterprise) | Multi-agent correctness and safety overview with full codebase context |
| Managed | Claude Security (Enterprise) | Hosted scanning that screens related repositories |
| In CI | Your present SAST and dependency scanners | Language-specific guidelines, supply-chain checks, coverage enforcement |
Key Takeaways
- The Claude Security plugin runs a six-phase multi-agent scan regionally in a Claude Code session, put in with /plugin set up claude-security@claude-plugins-official.
- Findings attain the report solely after a 3-voter adversarial panel (REACHABILITY, IMPACT, DEFENSES) clears a 2-of-3 quorum; a non-unanimous panel caps said confidence at medium.
- The verification tally is computed in code by the report renderer, not asserted by the mannequin, and stamped right into a per-commit revision file.
- Patches are constructed in a scratch clone, independently verified in opposition to three claims, and by no means utilized routinely.
- The scan provides no isolation of its personal — sandbox the session earlier than scanning code you don’t management.
Sources: Claude Security plugin documentation, Claude Security product page, Plugin source, claude-plugins-official, @claudeai announcement and Claude Security public beta blog
The put up Anthropic Releases Claude Security Plugin for Claude Code in Beta: A Multi-Agent Vulnerability Scanner That Runs in Your Terminal appeared first on MarkTechPost.
