Hunt map environment
Run threat hunting workflows for agentic IDEs like Claude Code, OpenCode, and Gemini in one command
npx -y skills add 3dcom2711/thrunt-god --skill hunt-map-environmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
SKILL.md
1.3 KB, 257 tokens by cl100k_base, as published. Nobody here has run it
Creates or updates:
.planning/environment/ENVIRONMENT.md.planning/MISSION.md.planning/HYPOTHESES.md.planning/STATE.md
Unknown tenants, tools, retention windows, access paths, and blind spots must remain TBD until the operator confirms them.
Confirmed environment facts should replace existing TBD markers immediately; only unresolved fields should stay TBD.
After this command: Run /hunt-shape-hypothesis or /hunt-plan 1.
</objective>
<execution_context> @.github/thrunt-god/workflows/hunt-map-environment.md @.github/thrunt-god/templates/environment-map.md </execution_context>
<process> Execute the environment-mapping workflow from @.github/thrunt-god/workflows/hunt-map-environment.md. Prefer concrete environment facts over generic best practices. Preserve existing analyst notes. Default behavior is to preserve confirmed facts and leave unknown values as `TBD` rather than populating simulated environment details. Replace `TBD` only where live workspace evidence or direct operator input confirms the fact. </process>