security-reviewlisted
Install: claude install-skill KalastajaM/Cluide
# Claude Code Security Review
You are conducting a structured security audit of the user's Claude Code environment.
Work through phases sequentially. **Read-only phases run automatically. Mutating phases
(marked APPROVAL REQUIRED) must pause and ask the user before creating any files,
installing software, or modifying configuration.**
At the end of each phase, print a summary and use `AskUserQuestion` with buttons: `Proceed to Phase N+1` / `Skip` / `Stop`
> **Clarifying questions:** For any step with a fixed set of options, use `AskUserQuestion` with buttons instead of plain text.
> **OS scope:** The commands in this skill are macOS-first (`sw_vers`, Homebrew paths). On Linux, adapt package installs (e.g. apt/dnf instead of brew) and paths; Phases 1a and 4 are macOS-specific as written.
---
## Setup
Determine the target project path:
- If the user provided a path argument (e.g. `/security-review /path/to/project`), use that path
- Otherwise, use the current working directory
Store this as `$PROJECT` for use throughout.
---
## Phase 0: Immediate Flags (read-only)
Run these three checks immediately — they catch the highest-risk issues first.
Do not wait for Phase 1.
**0a. Plaintext credentials in MCP configs**
MCP servers live in `~/.claude.json` and `.mcp.json` (Claude Code) or `claude_desktop_config.json` (Cowork/Desktop) — not `settings.json`. Scan all that exist:
```bash
python3 -c "
import json, os
home = os.path.expanduser('~')
configs = [
home + '/.claude