security-orchestrator

Runs a five-stage security audit pipeline and consolidates findings into a severity-sorted report.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill security-orchestrator-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-orchestrator
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/security-orchestrator
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill security-orchestrator-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running individual security checks in isolation leaves gaps: one tool audits RLS policies, another reviews authorization, and infrastructure threats go unchecked. This Skill chains five audit stages into one enforced sequence so a full-stack security review actually completes, with every finding consolidated into a single severity-ranked report. ## Core Features & Use Cases - Sequential 5-Stage Audit: Runs security-checklist (RLS, subscription state, rate limits, budget caps), authz-designer (endpoint authorization, IDOR scans, privilege escalation), paid-api-guard (six-layer defense for paid external APIs), /cso comprehensive (infrastructure, secrets, supply chain, STRIDE threat modeling), and /codex challenge (adversarial review). - Consolidated SUMMARY Report: Merges all stage outputs into docs/security/<date>-SUMMARY.md with issues sorted into Critical, High, Medium, and Low buckets. - Fix-and-Verify Loop: Drives atomic commits per issue, re-verification until Critical/High findings are resolved, and regression tests under tests/security/. - Use Case: Before a production release, ask for a full security audit; the Skill confirms scope and time budget, executes all five stages, writes per-stage reports, and blocks shipping until Critical and High issues are fixed. ## Quick Start Ask the agent to run a comprehensive security audit before deployment and confirm the audit scope and time budget when prompted.

Frequently Asked Questions about security-orchestrator

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

FAQPage Schema
How do I run a comprehensive security audit before deployment?

Request a full security audit and confirm the scope (application, infrastructure, payment, or all) plus a time budget. The orchestrator runs five stages in sequence—checklist, authorization review, paid API guard, infrastructure audit, and adversarial challenge—then produces a severity-sorted SUMMARY report.

What security areas does a full-stack audit cover?

The audit covers RLS policies, subscription state, dual rate limiting, budget caps, endpoint authorization middleware, IDOR vulnerabilities, privilege escalation, paid external API defenses, infrastructure secrets, supply chain, CI/CD, and STRIDE threat modeling.

When should I use a single security check instead of the full audit?

Use the narrow skills directly for scoped work: security-checklist for RLS only, authz-designer for permission models, paid-api-guard for payment APIs, or /cso for infrastructure only. The orchestrator is intended only for whole-stack audits.

Can I deploy if the security audit finds Critical issues?

No. Critical and High findings must be fixed with atomic commits, re-verified, and covered by regression tests before shipping. Deploying with unresolved Critical issues is an explicit anti-pattern in the workflow.

What happens if a project has no paid external API calls?

The paid-api-guard stage is skipped when no external paid API calls exist, but the skip reason is recorded explicitly. All other stages still run and their results feed into the consolidated SUMMARY report.