hunt-dispatch

To automatically load the correct skill set, you trigger the hunt-dispatch workflow by invoking it with mode=redteam or mode=wapt. This fingerprints the target environment and maps signals to platform-specific skills to drive the engagement workflow.

Target environment fingerprinting works by analyzing platform signals and mapping them to specific attack skills like okta-attack or m365-entra-attack. This deterministic workflow ensures the correct hunt-* sets are loaded for active testing.

The best way to manage multi-stage skill loading is using a deterministic workflow that loads an always-on base mindset, applies platform-specific fingerprints, loads high-impact hunt-* sets, and prints a taxonomy for session handoff.

No, you cannot use hunt-dispatch directly by name. It must be invoked with mode=redteam or mode=wapt to trigger skill loading and taxonomy printing, after which control is handed back to /hunt for active testing.

You need taxonomy printing for session handoff after receiving a /hunt mode answer and before probing live systems. This skill selects and prints the proper taxonomy for the operator to review during the engagement workflow.

Yes, hunt-dispatch supports fingerprinting for cloud IAM and supply chain attack recon. It maps target signals to platform skills including cloud-iam-deep, supply-chain-attack-recon, and apk-redteam-pipeline to load corresponding hunt-* sets.