octo-security

Security - Security Audit Skill

Your first output line MUST be: 🐙 Octopus Security Audit

🤖 INSTRUCTIONS FOR CLAUDE

MANDATORY COMPLIANCE — DO NOT SKIP

When the user explicitly invokes /octo:security, you MUST execute the structured security audit workflow below. You are PROHIBITED from doing a quick check directly, skipping the clarifying questions, or deciding the task is "too simple" for this workflow. The user chose this command deliberately — respect that choice.

EXECUTION MECHANISM — NON-NEGOTIABLE

You MUST dispatch work to external providers (Codex, Gemini, etc.) for this command. You are PROHIBITED from:

• ❌ Executing the entire task using only Claude-native tools
• ❌ Using a single Agent subagent instead of multi-provider dispatch
• ❌ Skipping provider dispatch because "I can handle this alone"

Multi-LLM orchestration is the purpose of this command. Single-model execution defeats its purpose.

---

When the user invokes this command (e.g., /octo:security <arguments>):

Step 1: Ask Clarifying Questions

CRITICAL: Before starting the security audit, use the AskUserQuestion tool to gather context:

Ask 3 clarifying questions to ensure targeted security assessment:

AskUserQuestion({
  questions: [
    {
      question: "What's the threat model for this application?",
      header: "Threat Model",
      multiSelect: false,
      options: [
        {label: "Standard web app", description: "Typical internet-facing application"},
        {label: "High-value target", description: "Handles sensitive data or finances"},
        {label: "Compliance-driven", description: "Must meet regulatory requirements"},
        {label: "API-focused", description: "Primarily API endpoints and integrations"}
      ]
    },
    {
      question: "What compliance requirements apply?",
      header: "Compliance",
      multiSelect: true,
      options: [
        {label: "None specific", description: "General security best practices"},
        {label: "OWASP Top 10", description: "Standard web security vulnerabilities"},
        {label: "GDPR/HIPAA/PCI", description: "Data protection regulations"},
        {label: "SOC2/ISO27001", description: "Enterprise security frameworks"}
      ]
    },
    {
      question: "What's your risk tolerance?",
      header: "Risk Level",
      multiSelect: false,
      options: [
        {label: "Strict/Zero-trust", description: "Maximum security, flag everything"},
        {label: "Balanced", description: "Industry-standard security posture"},
        {label: "Pragmatic", description: "Focus on high/critical issues only"},
        {label: "Development-only", description: "Non-production environment"}
      ]
    },
    {
      question: "How should findings be validated? Multi-LLM options use Claude + Codex + Gemini together.",
      header: "Multi-LLM Validation",
      multiSelect: false,
      options: [
        {label: "Standard audit", description: "Claude-only security analysis (no external API costs)"},
        {label: "Multi-LLM red team debate", description: "Codex plays blue team, Gemini plays red team, Claude synthesizes (recommended for high-value targets)"},
        {label: "Full Multi-LLM adversarial cycle", description: "4-phase blue→red→remediate→validate with three-model debate at each transition"},
        {label: "Multi-LLM debate on critical findings only", description: "Standard audit, then Claude + Codex + Gemini debate any critical/high severity findings"}
      ]
    }
  ]
})