cabinet-security

Audit Claude Code projects for security risks and data exposure issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cabinet-security
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/cabinet-security
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures basic security hygiene for Claude Code projects by preventing accidental data exposure, weak configurations, and vulnerable dependencies.

Core Features & Use Cases

  • Automated checks: dependency vulnerability scans, secret scans, and repository history reviews to surface potential exposures.
  • Investigation protocol: a two-stage process that guides you from automated findings to reasoned risk conclusions.
  • Guidance for API/server and deployment security, including input validation, auth exposure, and environment variable handling.

Quick Start

Run a security audit pass on your Claude Code project to surface exposure risks and recommended mitigations.

Frequently Asked Questions about cabinet-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Claude Code project for security risks and data exposure?▼

To audit your Claude Code project for security risks, you run an automated pass that scans dependencies, checks for exposed secrets, and reviews repository history to surface potential data exposure issues.

What is the best way to prevent accidental data exposure during deployment planning?▼

The best way to prevent accidental data exposure during deployment planning is by enforcing deployment hygiene, verifying environment variable handling, and checking authentication configurations before release.

How does a two-stage investigation protocol work for dependency vulnerability scans?▼

The two-stage investigation protocol for dependency scans works by first gathering automated vulnerability findings, then guiding you through a reasoned analysis to reach a final risk conclusion.

Can I use automated secret scans for code review in small teams?▼

Yes, you can use automated secret scans during code review for small teams to enforce basic security hygiene, detect weak configurations, and prevent accidental data exposure before merging changes.

What security checks should I run for API and server deployment hygiene?▼

Security checks for API and server deployment hygiene should include input validation analysis, authentication exposure review, environment variable handling verification, and dependency vulnerability scans.