agentleFS
LeostrukaLeostruka/devin-bundle/skills/net-probe/SKILL.md

net-probe

Skill0 starsChanged 3 months agoMITView on GitHub

Use when probing declared hosts or networks under an engagement contract (port/service scan, SMB/AD enumeration, TLS audit, vulnerability scan). Routes to extensions/offsec-tools/wrapper.py tools: nmap, masscan, netexec, enum4linux-ng, testssl.sh, openvas. Verify-not-exploit by default.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify-not-exploit default: prove exposure, do not pivot or persist.

    line 53
  2. Distinctive:

    No credential harvesting (no dumping LSASS/NTDS, no relay-to-auth).

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Net Probe

Network/infrastructure offensive testing under contract, via extensions/offsec-tools/wrapper.py (domain net).

Contract (mandatory)

--target (host/CIDR), --window, --roe. ROE states scan rate, excluded hosts, and whether credentialed checks are in scope.

Tools

ToolModeUse
nmapactiveport/service/version scan, NSE scripts
masscanactivehigh-rate discovery; raw-socket (WSL preferred)
netexecactiveSMB/WinRM/LDAP enumeration and checks
enum4linux-ngactiveSMB/RPC user/share enumeration
testssl.shpassiveTLS config/cipher audit
openvasactivefull vuln scan (Docker GVM stack)

Commands

W=extensions/offsec-tools/wrapper.py

python $W run --tool nmap --target 10.0.0.5 --window "..." --roe "..." \
  --confirm -- -sV -Pn --top-ports 1000 10.0.0.5
python $W run --tool netexec --target 10.0.0.0/24 --window "..." \
  --roe "..." --confirm --backend wsl -- smb 10.0.0.0/24
python $W run --tool testssl.sh --target t.example:443 --window "..." \
  --roe "..." --backend wsl

Backend: native first; masscan/testssl.sh/netexec are usually healthier on wsl. openvas is docker-only and heavy -- confirm the engagement actually needs it.

Evidence

Per finding: probe argv, backend, raw output excerpt, confidence. Scanner output is a lead, not a finding -- verify with a targeted probe before reporting confirmed.

Boundaries

  • Verify-not-exploit default: prove exposure, do not pivot or persist.
  • No credential harvesting (no dumping LSASS/NTDS, no relay-to-auth).
  • Excluded hosts/rates in ROE are hard stops.

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.