SKILLEMALL.ai
GitHub ↗ RU Sign in

BC ethical-hacking-methodology

Master the complete penetration testing lifecycle from reconnaissance through reporting. This skill covers the five stages of ethical hacking methodology, essential tools, attack techniques, and professional reporting for authorized security assessments.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 898 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Master the complete penetration testing lifecycle from reconnaissance through reporting.

As a process C 60/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting

ProcedureData and analyticsResearchSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
90
Quality 40%
81
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: ethical-hacking-methodology (sickn33/agentic-awesome-skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 6

    ✓ No critical or high findings

    Medium and low: 6
    • medium Dangerous commands cmd-persistence SKILL.md:302
      Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)
      echo "* * * * * /tmp/backdoor.sh" >> /etc/crontab
      security skill
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      description: "Master the complete penetration testing lifecycle from reconnaissance through reporting. This skill covers the five stages of ethical hacking methodology, essential tools, attack techniq
      quoted
    • low Risky intent intent-offensive-security SKILL.md:24
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      > AUTHORIZED USE ONLY: Use this skill only for authorized penetration testing engagements, defensive validation, or controlled educational environments.
    • low Risky intent intent-offensive-security SKILL.md:30
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Master the complete penetration testing lifecycle from reconnaissance through reporting. This skill covers the five stages of ethical hacking methodology, essential tools, attack techniques, and profe
    • low Risky intent intent-offensive-security SKILL.md:60
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - Conduct penetration testing with permission
    • low Risky intent intent-offensive-security SKILL.md:305
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      **Privilege Escalation**

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 124 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2898 tokens

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 254: enough signal without eating the budget
    • +4Structure: 27 headings
    • +3Step-by-step instructions: 124 items
    • +4Has examples (13 code blocks)

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