agentleFS
pashki975pashki975/thm-claude-kit/.claude/skills/thm-methodology/SKILL.md

thm-methodology

Skill2 starsChanged 4 months agoMITView on GitHub

Standard operating procedure for solving a TryHackMe box. Use when starting a new room, when the user asks "what next", or when stuck and needing a methodical next step. Guides the recon → enum → foothold → privesc → loot flow and enforces scope discipline.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this flow. Never skip enumeration to jump to exploitation.

    line 8
  2. Distinctive:

    Create room folder + scans/ + notes.md

    line 12
  3. Very specific:

    Don't forget UDP — SNMP/TFTP/DNS hide there (/enum-udp).

    line 16
  4. Distinctive:

    Run local enum with the checklist (/linux-privesc): sudo -l, SUID, capabilities, cron/pspy, cred hunting

    line 37
  5. Distinctive:

    Check the foothold for a second NIC / internal subnet (ip a, ip route, arp -a)

    line 42
  6. Distinctive:

    When stuck: re-read scan output, try a bigger wordlist, check UDP, check for vhosts, revisit versions

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

TryHackMe Methodology

Follow this flow. Never skip enumeration to jump to exploitation.

0. Setup

  • Confirm VPN up and target reachable (/vpn-check)
  • Create room folder + scans/ + notes.md

1. Recon

  • Full TCP port scan, then targeted -sV -sC on open ports (/recon)
  • Don't forget UDP — SNMP/TFTP/DNS hide there (/enum-udp). Run it in parallel with TCP enum.
  • Record every open port/service in notes.md

2. Enumerate per service

Match each open port to its enumeration path:

  • 80/443/8080 → web (/enum-web): dirs, vhosts, tech stack, source, robots.txt
  • 139/445 → SMB (/enum-smb)
  • 21 → FTP: try anonymous login
  • 22 → SSH: note version, save creds for later; don't brute unless hinted
  • 25/110/143 → mail
  • 3306/1433/5432/27017/6379 → databases (/db-enum): creds to reuse + RCE paths
  • 161/69/53 (UDP) → /enum-udp
  • Map service versions to CVEs (cve-researcher agent)

3. Foothold

  • Exploit the most promising verified vector
  • Set up listener + payload (/listener) for reverse shells
  • Upgrade to a stable TTY immediately after landing a shell

4. Post-exploitation / privesc

  • Grab the user flag
  • Run local enum with the checklist (/linux-privesc): sudo -l, SUID, capabilities, cron/pspy, cred hunting
  • Analyze with privesc-advisor agent
  • Escalate to root, grab root flag

5. Pivot (if the room has more than one host)

  • Check the foothold for a second NIC / internal subnet (ip a, ip route, arp -a)
  • Tunnel in (/tunnel) with ligolo-ng, chisel, sshuttle, or SSH forwards
  • Record each internal host in notes.md as a new target and re-run this methodology against it

6. Loot & document

  • Record all flags and creds in notes.md
  • Generate writeup (report-writer agent)

Rules

  • Stay strictly on the assigned target IP/range
  • Enumerate thoroughly before exploiting — most CTF blockers are missed enum
  • Reuse found credentials everywhere (SSH/SMB/web/db) — password reuse is rampant on THM
  • When stuck: re-read scan output, try a bigger wordlist, check UDP, check for vhosts, revisit versions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.