SKILLEMALL.ai

CC building-red-team-c2-infrastructure-with-havoc

Deploy and configure the Havoc C2 framework (teamserver, HTTPS/HTTP/SMB listeners, Nginx redirectors, and Demon agents) with malleable traffic profiles and OPSEC-hardened infrastructure for authorized red team operations. Use when standing up or hardening Havoc C2 infrastructure for a written, authorized adversary emulation engagement.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 2 241 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Deploy and configure the Havoc C2 framework (teamserver, HTTPS/HTTP/SMB listeners, Nginx redirectors, and Demon agents) with malleable traffic profiles and…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

GeneratorGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
79/100
safety, quality, tests
Safety 60%
84
Quality 40%
71
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 16

    ✓ No critical or high findings

    Medium and low: 16
    • low Risky intent intent-offensive-security assets/template.md:81
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | pivot.exe | Service EXE | SMB Pivot | x64 | [hash] | Lateral movement |
    • low Risky intent intent-offensive-security references/api-reference.md:1
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # API Reference: Red Team C2 Infrastructure with Havoc
    • low Risky intent intent-offensive-security references/api-reference.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      > For authorized penetration testing and lab environments only.
    • low Risky intent intent-offensive-security references/api-reference.md:47
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## Payload Generation
    • low Risky intent intent-offensive-security references/standards.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### Command and Control (TA0011)
    • low Risky intent intent-offensive-security references/standards.md:43
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **NIST SP 800-115** - Section 4.3: Penetration Testing (authorized C2 usage)
    • low Risky intent intent-offensive-security references/standards.md:44
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **NIST SP 800-53 Rev. 5** - CA-8: Penetration Testing controls
    • low Risky intent intent-offensive-security references/standards.md:60
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - Authorized penetration testing under PCI DSS 11.4, SOC 2 CC7.1
    • low Risky intent intent-offensive-security references/standards.md:61
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - TIBER-EU / CBEST threat-led penetration testing frameworks
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      description: Deploy and configure the Havoc C2 framework (teamserver, HTTPS/HTTP/SMB
    • low Risky intent intent-offensive-security SKILL.md:5
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      OPSEC-hardened infrastructure for authorized red team operations. Use when standing
    • low Risky intent intent-offensive-security SKILL.md:43
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Building Red Team C2 Infrastructure with Havoc
    • low Risky intent intent-offensive-security SKILL.md:47
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      Havoc is a modern, open-source post-exploitation command and control (C2) framework created by C5pider. It provides a collaborative multi-operator interface similar to Cobalt Strike, featuring the Dem
      detector
    • low Risky intent intent-offensive-security SKILL.md:52
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - When deploying or configuring building red team c2 infrastructure with havoc capabilities in your environment
    • low Secrets in code secret-password-literal SKILL.md:134
      Hard-coded password / key literal (may be an example)
      Password = "Str0ngP@ssw0rd!"
    • low Secrets in code secret-password-literal SKILL.md:137
      Hard-coded password / key literal (may be an example)
      Password = "An0th3rP@ss!"

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "nist_ai_rmf"
    • note frontmatter-key unknown frontmatter key "d3fend_techniques"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 6 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 13 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2241 tokens
    • low 13 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • -43 reference files, but SKILL.md never points to them: the model will not open them
    • -32 of 2 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +3Description length 337: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (7 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.