lean-net
Skill2 starsChanged 56 days agoMITView on GitHub
Runs token-efficient defensive network and exposure reviews for Cursor and Codex. Inventories bind addresses, published ports, security groups, and Kubernetes/Docker listeners from local config, then reports compact hardening fixes. Use when the user asks for network security, firewall review, security groups, open ports, TLS listeners, Docker/K8s exposure, or segmentation. Do not use for scanning third-party networks, packet crafting, exploits, or unauthorized access.
In this repository21 other files it gives its agents.
- lean-cryptoSkill
- lean-mobileSkill
- lean-privacySkill
- lean-secSkill
- lean-webSkill
- lean-a11ySkill
- lean-depsSkill
- lean-docsSkill
- lean-perfSkill
- lean-reviewSkill
- lean-ciSkill
- lean-cloudSkill
- lean-costSkill
- lean-hardeningSkill
- lean-iotSkill
- lean-dfirSkill
- lean-ir-playbookSkill
- lean-malwareSkill
- lean-osintSkill
- lean-phishSkill
- lean-threat-modelSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Do not run nmap, masscan, or cloud APIs against hosts the user did not name as theirs.
- Very specific: line 31
Default lean. deep only if asked.
- Very specific: line 41
Run expose. Treat 0.0.0.0/0, hostNetwork, Docker ports: to all interfaces, and plaintext listeners as the first queue.
- Distinctive: line 48
No exploit, spoofing, or packet-injection steps.
≈ “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.
Files
Lean Net
Defensive exposure review of local config, not of the internet. Scripts list listeners; you confirm a few files; you patch only when asked.
Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.
python3 "$SKILL_ROOT/scripts/lean_net.py" expose .
python3 "$SKILL_ROOT/scripts/lean_net.py" trim --chars 2500 path/to/out.txtDo not run nmap, masscan, or cloud APIs against hosts the user did not name as theirs. If they already have a pcap/log, summarize it with trim; do not dump packets.
Mode
Default lean. deep only if asked.
| Mode | Budget |
lean | expose + up to 8 slices; references/exposure.md; ≤6 findings |
standard | up to 16 slices; ≤10 findings |
deep | needed refs only; ≤16 findings |
Workflow
- Run
expose. Treat0.0.0.0/0,hostNetwork, Dockerports:to all interfaces, and plaintext listeners as the first queue. - Slice-read compose, Ingress, Terraform SG, nginx listen lines.
- Report bind, CIDR, TLS, and egress. Stop unless asked to patch.
Hard rules
- Config and code in this workspace only. No live port scans of third parties.
- No exploit, spoofing, or packet-injection steps.
- Cap quotes at 12 lines. Never paste a full pcap or flow log.
Report template
## Lean-net (`<mode>`)
**Asset:** <vpc/compose/cluster> | **Budget:** files_read=<n>
| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | public bind / open CIDR | tighten CIDR, bind localhost, require TLS |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
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.