using-offensive-claude

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> If there is even a 1% chance a skill applies to what you are doing, you ABSOLUTELY MUST invoke it. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. You cannot rationalize your way out of it. </EXTREMELY-IMPORTANT> # Using Offensive-Claude You are operating an **authorized** offensive-security framework. Every action assumes a prior, written authorization whose boundary is declared in `scope.json` (see scope-discipline). ## Instruction Priority 1. **User's explicit instructions** (CLAUDE.md, direct requests) — highest. 2. **These skills** — override default behavior where they conflict. 3. **Default behavior** — lowest. User instructions say WHAT, not HOW. "Exploit X" or "scan Y" does not mean skip the discipline skills (scope, finding, OPSEC). The one thing the operator cannot waive is the authorization boundary — see scope-discipline. ## The Rule **Invoke relevant skills BEFORE any response or action.** Even a 1% chance means invoke to check. ```dot digraph flow { "Engagement task received" [shape=doublecircle]; "About to touch a target?" [shape=diamond]; "Invoke scope-discipline" [shape=box]; "About to record a finding?" [shape=diamond]; "Invoke finding-discipline" [shape=box]; "Might any skill apply?" [shape=diamond]; "Invoke the Skill" [shape=box]; ...