help
CommandShow available THRUNT threat hunting commands and artifact layout
Publish a hunt as a case report, escalation, detection promotion, or leadership summary
name: hunt:publish description: Publish a hunt as a case report, escalation, detection promotion, or leadership summary argument-hint: "[target]" allowed-tools: - Read - Bash - Write - AskUserQuestion
<objective> Publish the current hunt in the right format for action.
**Creates or updates:**
**After this command:** Route to follow-on hunting, escalation, or detection engineering based on the outcome. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/hunt-publish.md </execution_context>
<process> Execute the publishing workflow from @~/.claude/thrunt-god/workflows/hunt-publish.md. Choose the smallest publish format that drives action without overstating confidence. </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
Execute a hunt phase with parallel telemetry work, query logging, receipt generation, and optional wave targeting
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…