help
CommandShow available THRUNT threat hunting commands and artifact layout
Add phase to end of current milestone in huntmap
name: thrunt:add-phase description: Add phase to end of current milestone in huntmap argument-hint: <description> allowed-tools: - Read - Write - Bash
<objective> Add a new integer phase to the end of the current milestone in the huntmap.
Routes to the add-phase workflow which handles:
</objective>
<execution_context> @~/.claude/thrunt-god/workflows/add-phase.md </execution_context>
<context> Arguments: $ARGUMENTS (phase description)
Huntmap and state are resolved in-workflow via `init phase-op` and targeted tool calls. </context>
<process> **Follow the add-phase workflow** from `@~/.claude/thrunt-god/workflows/add-phase.md`.
The workflow handles all logic including: 1. Argument parsing and validation 2. Huntmap existence checking 3. Current milestone identification 4. Next phase number calculation (ignoring decimals) 5. Slug generation from description 6. Phase directory creation 7. Huntmap entry insertion 8. STATE.md updates </process>
Show available THRUNT threat hunting commands and artifact layout
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
Publish a hunt as a case report, escalation, detection promotion, or leadership summary
Audit a file, directory, or whole repo for insecure default configuration: fallback secrets, default credentials, fail-open…
Check text against AGT prompt-injection, context-poisoning, and MCP threat detectors.
Show which external bug-bounty tools are installed on this machine and print install hints for the missing ones. Curated from…