Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From security-engineering
Stand up tuned SAST/SCA/secret-scanning/DAST gates in CI with exploitability-based triage.
How this command is triggered — by the user, by Claude, or both
Slash command
/security-engineering:setup-appsec-gate [stack + CI + current scanning]The summary Claude sees in its command listing — used to decide when to auto-load this command
You are running `/security-engineering:setup-appsec-gate`. Use `appsec-engineer` + the `appsec-scanning` skill. ## Steps 1. Place SAST+SCA on PR, DAST on a deployed build, secret-scanning on every commit. 2. Tune for signal; define triage by exploitability×blast-radius. 3. Add class-level fixes + lint rules for recurring patterns. 4. State that verdicts route to security-reviewer. 5. Emit the gate (from `templates/security-ci-gate.md`) + Structured Output block.
You are running /security-engineering:setup-appsec-gate. Use appsec-engineer + the appsec-scanning skill.
templates/security-ci-gate.md) + Structured Output block.npx claudepluginhub mcorbett51090/ravenclaude --plugin security-engineering