Menu

Individual skill

claude-security

0upvotes

Claude Security: scan the codebase (the whole repository or a scoped part of it), scan changes (this branch's or a pull request's diff, or one commit), or suggest patches (findings turned into targeted patch files, each verified by a panel of agents, that you apply when you choose). Use when the user asks to scan, audit or check code with Claude Security, to scan their changes with Claude Security, or to fix or patch Claude Security findings.

plugins/claude-security/skills/claude-security/SKILL.md

Read pinned source

Source commit a7ba5b93db0c7c8d17f3f1d25853adca79598a1a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
46,580
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Claude Security

- Session start time (UTC): !`date -u +%Y%m%d-%H%M%S`

## The front-desk menu

This is the front desk. Its whole purpose is to work out which job the user wants and drive it, following that job's recipe.

1. **If the user already asked for a specific job** — in the arguments (`$ARGUMENTS`) or in plain text ("scan this repo", "scan my branch", "fix the findings", a bare commit sha) — do that job directly and skip the menu. The recipe still asks its own single follow-up question wherever the request left one open.
2. **Otherwise, open with the menu.** Call AskUserQuestion once, single select, `header: "Job"`, `question: "What would you like to do?"`, offering exactly these three options (never invent others — the tool adds its own free-text entry). The menu is your first user-visible act; no text of any kind comes before it.

   Offer these three options:
   1. [Scan codebase](${CLAUDE_SKILL_DIR}/jobs/scan-codebase.md)
   2. [Scan changes](${CLAUDE_SKILL_DIR}/jobs/scan-changes.md)
Back to top