hunt-oauth
⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:
- Ask the user to state the exact target URL, IP, account, or resource.
- Ask the user to confirm written authorization and the permitted scope.
- Show the exact command(s) and explain their expected effect.
- Wait for explicit confirmation in the current conversation.
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
Test boundaries
Use only authorized test accounts, exact scoped origins and reversible linking actions. Dynamic registration creates resources and needs explicit scope plus cleanup. Do not claim dangling cloud resources or access third-party identity-provider infrastructure without separate permission. Audience acceptance depends on the intended resource API; a token from another client is not necessarily intended for another audience. Never print live tokens, codes or secrets to terminal history or shared logs.