From security-engineering
Stand up tuned application security scanning in CI: SAST + SCA per-PR, DAST on a deployed build, secret-scanning, and triage by exploitability×blast-radius rather than raw CVSS.
How this skill is triggered — by the user, by Claude, or both
Slash command
/security-engineering:appsec-scanningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** catch vulnerabilities early and act on the real ones.
Purpose: catch vulnerabilities early and act on the real ones.
Rank by exploitability × blast radius, not CVSS alone. Reachability beats severity: a 9.8 in dead code < a 6.5 on an unauthenticated endpoint.
One SQLi -> parameterize everywhere + a lint rule. Don't whack-a-mole instances.
Propose the control + residual risk; security-reviewer decides ship/no-ship.
npx claudepluginhub mcorbett51090/ravenclaude --plugin security-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.