disabled-c2-policy

To enforce C2 policy boundaries, this skill automatically blocks high-risk command-and-control infrastructure requests and requires explicit repository configuration, engagement-specific consent, and valid authorization metadata before unlocking any workflows.

When you request C2 listener configuration or beaconing techniques, the skill intervenes to explain the strict refusal policy, verifies your authorization metadata, and routes you toward analyzing detection gaps instead.

No, you cannot use this skill for offensive evasion technique deployment. It explicitly refuses high-risk infrastructure requests and redirects authorized pentest engagements toward defensive alternatives like egress control reviews and purple-team tabletop exercises.

Yes, unlocking any C2 policy workflows requires explicit repository configuration, engagement-specific consent, and valid authorization metadata to ensure strict governance over command-and-control activity within authorized pentest boundaries.

Instead of deploying C2 infrastructure, the policy routes you to defensive alternatives including detection engineering, egress control reviews, purple-team tabletop exercises, and architecture review to promote secure boundaries.