help
CommandShow available THRUNT threat hunting commands and artifact layout
Validate hunt conclusions against receipts, contradictory evidence, and success criteria
name: hunt:validate-findings description: Validate hunt conclusions against receipts, contradictory evidence, and success criteria argument-hint: "[phase]" allowed-tools: - Read - Bash - Write - AskUserQuestion
<objective> Validate the current hunt's findings.
`FINDINGS.md` and `EVIDENCE_REVIEW.md` remain the source of truth for validation.
**Creates or updates:**
**After this command:** Run `/hunt:publish`. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/hunt-validate-findings.md @~/.claude/thrunt-god/templates/findings.md @~/.claude/thrunt-god/templates/evidence-review.md </execution_context>
<process> Execute the validation workflow from @~/.claude/thrunt-god/workflows/hunt-validate-findings.md. Mark each hypothesis as supported, disproven, or inconclusive. Call out evidence gaps explicitly. </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…