abort-template
Abort / crisis plan generator — halt triggers, response actions, AI-aware safety gates (hallucination threshold, destructive-action gate, output validation).
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-12
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- abort-template
- metadata
- { "tags": "abort, halt, crisis, safety, ai-safety, owasp-agentic", "subdomain": "planning", "when_to_use": "create abort plan, emergency halt, crisis procedure, AI safety gate, hallucination guard, destructive action gate", "upstream_ref": "Soundwave abort / crisis template — halt triggers, AI-safety gates, hallucination guardrail" }
- description
- Abort / crisis plan generator — halt triggers, response actions, AI-aware safety gates (hallucination threshold, destructive-action gate, output validation).
- allowed-tools
- Read Write Edit
03 SKILL.md 正文
Abort / Crisis Plan Generator
The abort plan defines when the agent stops. Without it, the autonomous loop runs through real-incident alerts, scope violations, and production-data exposures as if they were normal operations.
AI-specific gates address the failure modes documented in OWASP Top 10 for Agentic Applications (2025.12) — hallucination, prompt injection, unverified destructive actions.
When to Use
- After CONOPS + Threat Profile + Data Handling are written (the kill chain shapes which triggers are relevant)
- User says "create abort plan", "halt triggers", "emergency stop", "safety gates"
Workflow
Step 1: Keep the Three Default Triggers
The AbortPlan schema seeds three default halt triggers. Keep all three; do not remove unless the engagement is explicitly read-only:
EMERGENCY— Real-incident alert from blue team / SOCCRITICAL— Production data observed in collected evidenceCRITICAL— Scope boundary violation detected
Step 2: Add Engagement-Specific Triggers
Based on the interview answers, add custom AbortTrigger entries. Common additions:
| Engagement signal | Severity | Response |
|---|---|---|
| Tier-3+ adversary emulation against critical infrastructure | EMERGENCY |
Halt + operator-page + 1hr cooldown |
| Compliance-bound data class encountered (GDPR / HIPAA) | CRITICAL |
Halt; redact; await operator |
| Network outage or latency spike on target | WARNING |
Pause active scanning; resume after 5min |
| LLM cost-per-objective threshold exceeded | WARNING |
Pause; ask operator to approve budget |
| C2 beacon lost for > 30 minutes during active phase | WARNING |
Pause; re-establish C2 before continuing |
Step 3: Set AI Safety Gates
hallucination_threshold— default 3 (after 3 unverified-success claims, force evidence-collection mode). Lower (2) for high-stakes engagements; never set 0.destructive_action_gate— default True. Set False only for read-only / recon-only engagements where norm,drop,format,delete-policycommands will run.output_validation— default"verify-evidence-hash". Override to"second-tool-confirm"for engagements where evidence cannot be hashed (e.g. real-time API responses).
Step 4: Set Abort Signal Channel + Recovery Procedure
abort_signal_channel— operator's out-of-band channel for forcing halt (HTTP endpoint, file marker, ask_user_question). Leave empty only if Ctrl+C-via-CLI is the only abort path.recovery_procedure— default text covers the standard flow (snapshot → export evidence → run cleanup → operator approval). Override for engagements with custom recovery semantics.
Validation Checklist
Before writing plan/abort.json:
- [ ] At least one
EMERGENCY-severity trigger exists - [ ] All custom triggers have non-empty
conditionandresponse_action - [ ]
hallucination_threshold≥ 1 - [ ]
output_validationmatches one of the documented methods - [ ]
abort_signal_channelis set OR explicitly marked "CLI Ctrl+C only"
Anti-patterns
- Removing the EMERGENCY default — guarantees the agent runs through a SOC real-incident alert
- Setting
destructive_action_gate=Falsefor engagements that include post-exploit or cleanup phases - Conflating WARNING and CRITICAL — WARNING pauses one step; CRITICAL halts the active objective
Output
Write to plan/abort.json validating against decepticon.core.schemas.AbortPlan.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.