Individual skill

hunt-run

0upvotes

Execute a hunt phase with parallel telemetry work, query logging, receipt generation, and optional wave targeting

thrunt-god/examples/brute-force-to-persistence/.github/skills/hunt-run/SKILL.md

Read pinned source

Source commit 6c1a49a70ff09453f4a95f47774b9cd5fabbc02f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 41
Repository last updated: Jul 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agents Repository topic
ai-agent Repository topic
ai-agents Repository topic
claude-code Repository topic
detection-engineering Repository topic
threat-detection Repository topic
threat-hunting Repository topic
threat-intelligence Repository topic
thrunt Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,513 bytes

Read excerpt


<objective>
Execute a hunt phase.

Documented flags are available behaviors, not implied active behaviors.
Treat `--wave N`, `--gaps-only`, and `--interactive` as active only when the literal token appears in `$ARGUMENTS`.
If none of these tokens appear, run the standard full-phase execution flow.

The execution boundary is the shared THRUNT runtime contract:
- each material hunt action is shaped as a `QuerySpec`
- connectors return one normalized result envelope
- query logs and receipts are emitted from runtime metadata, not connector-specific ad hoc blobs
- connector-backed execution can be inspected locally with `thrunt-tools runtime list-connectors`, `thrunt-tools runtime doctor`, `thrunt-tools runtime smoke`, `thrunt-tools pack render-targets`, and `thrunt-tools runtime execute`

`--wave N` executes only a single wave and must not mark the whole phase complete until no incomplete plans remain.