Establish what's security-relevant about this repo before an Intercept scan or hunt — detect the stack from the code, ask the platform (get_repo_context) what it already knows, and confirm only the gaps it can't infer. Never writes anything into the repo. Use at the start of /intercept:scan and /intercept:hunt, or when the user mentions where they deploy, what they build, or their cloud/runtime.
$npx -y skills add hijacksecurity/claude-plugins --skill intercept-stack-contextInstalls into the current project.
Run `npx skills use "https://github.com/hijacksecurity/claude-plugins" --skill "hijacksecurity/claude-plugins/intercept-stack-context"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/hijacksecurity/claude-plugins" that are relevant to the current task. Run `npx skills add "https://github.com/hijacksecurity/claude-plugins"` and select the relevant skills, then follow their instructions.