firewall
Skill0 starsChanged 53 days agoMITView on GitHub
Firewall rule management (ufw / iptables / nftables). Use when: opening or restricting ports, configuring inbound/outbound rules on an authorized server; closing port 22 is forbidden (needs explicit --mode yes), ufw disable / iptables -F go through confirmation. Boundary: authorized servers only.
In this repository27 other files it gives its agents.
- mysql-opsSkill
- redis-opsSkill
- data-opsSkill
- docker-containerSkill
- docker-imageSkill
- docker-installSkill
- docker-opsSkill
- apt-repoSkill
- file-opsSkill
- server-settingsSkill
- shell-execSkill
- infra-opsSkill
- ssh-terminalSkill
- bbrSkill
- net-secSkill
- ssh-keysSkill
- monitorSkill
- process-manageSkill
- obs-opsSkill
- opsSkill
- lnmpSkill
- nginx-rewriteSkill
- php-manageSkill
- reverse-proxySkill
- site-manageSkill
- web-stackSkill
- ssl-manageSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Do not open unnecessary public ports.
- Very specific: line 23
Run ufw/iptables rules via shell-exec.
≈ “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
firewall
Capabilities
- Port open / close
- Rule add / remove / list
- ufw / firewalld / iptables three backends
Safety gate
- Closing SSH port (22):
ufw deny 22/ufw delete/ufw disablego through warnlist (--mode autodenies, needs--mode yes) iptables -F/-Pgo through warnlist confirmation- Do not open unnecessary public ports; audit every run (host + exit code)
EXECUTION (real engine)
Run ufw/iptables rules via shell-exec.
opsctl shell-exec --host web1 --cmd "ufw allow 80,443/tcp" --mode yes
opsctl shell-exec --host web1 --cmd "ufw enable" --mode yes⚠️ The safety gate marks ufw disable, iptables -F|-P, ufw deny 22, ufw delete as confirm (not permanently blocked):
--mode auto denies by default; --mode yes or interactive can allow. Before closing 22, make sure a working key session already exists.
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.