Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/iamnolanhu/digitalocean-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/iamnolanhu/digitalocean-skills/do-firewall)<a href="https://agentmods.dev/commands/iamnolanhu/digitalocean-skills/do-firewall"><img src="https://agentmods.dev/badge/commands/iamnolanhu/digitalocean-skills/do-firewall.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00008 | $0.00729 |
| Opus 5 | $0.00004 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
do-firewall scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firewall Management
Handle common firewall operations based on the action specified.
Actions
list
Show all firewalls with summary of rules and assigned Droplets.
firewall-list
Format output as:
| Name | Inbound Rules | Outbound Rules | Droplets |
|------|---------------|----------------|----------|
| fw-prod-web | 3 | 1 | 2 |
show <name>
Display detailed firewall rules for a specific firewall.
firewall-get Name=<name>
Format as readable rule list:
## fw-prod-web
Inbound:
- TCP 443 from 0.0.0.0/0 (HTTPS)
- TCP 80 from 0.0.0.0/0 (HTTP)
- TCP 22 from 203.0.113.0/24 (SSH from office)
Outbound:
- All traffic to 0.0.0.0/0
Droplets: prod-web-01, prod-web-02
allow <name> <port>
Add inbound rule allowing traffic on specified port from anywhere.
firewall-add-rules:
FirewallID: <get from firewall-list by name>
InboundRules:
- Protocol: tcp
Ports: "<port>"
Sources:
Addresses: ["0.0.0.0/0", "::/0"]
allow <name> <port> <source>
Add inbound rule allowing traffic from specific source CIDR.
firewall-add-rules:
FirewallID: <get from firewall-list by name>
InboundRules:
- Protocol: tcp
Ports: "<port>"
Sources:
Addresses: ["<source>"]
deny <name> <port>
Remove inbound rule for specified port.
firewall-remove-rules:
FirewallID: <get from firewall-list by name>
InboundRules:
- Protocol: tcp
Ports: "<port>"
Sources:
Addresses: ["0.0.0.0/0", "::/0"]
apply <name> <droplet-name-or-id>
Apply firewall to a Droplet.
firewall-add-droplets:
FirewallID: <get from firewall-list by name>
DropletIDs: [<get from droplet-list by name>]
remove <name> <droplet-name-or-id>
Remove firewall from a Droplet.
firewall-remove-droplets:
FirewallID: <get from firewall-list by name>
DropletIDs: [<get from droplet-list by name>]
Examples
/do-firewall list
/do-firewall show fw-prod-web
/do-firewall allow fw-prod-web 443
/do-firewall allow fw-prod-web 22 203.0.113.0/24
/do-firewall deny fw-prod-web 8080
/do-firewall apply fw-prod-web prod-api-01
/do-firewall remove fw-prod-web dev-test-01
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 132 lines · 8 tokens per session scan A 8a1fae766c12
do-firewall is a command published in the GitHub repository iamnolanhu/digitalocean-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 729 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.