Waf Setup
ListedAutomates Web Application Firewall (WAF) configuration based on provided rulesets and deployment environment.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bagelhole/devops-security-agent-skills --skill waf-setup -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bagelhole
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.cloudflare.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.cloudflare.comundeclaredWhat it found
- security/network/waf-setup/SKILL.md:240contacts api.cloudflare.com
curl -s "https://api.cloudflare.com/client/v4/zones/${ZONE_ID}/rulesets" \ - security/network/waf-setup/SKILL.md:244contacts api.cloudflare.com
curl -X POST "https://api.cloudflare.com/client/v4/zones/${ZONE_ID}/rulesets" \ - security/network/waf-setup/SKILL.md:276contacts api.cloudflare.com
curl -X POST "https://api.cloudflare.com/client/v4/zones/${ZONE_ID}/rulesets" \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bagelhole/devops-security-agent-skills at 0365f57a07.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0365f57a07
- Scanned
- 2 files, 615 lines
About this skill
What it does
The waf-setup skill automates the configuration and deployment of Web Application Firewalls (WAFs). It can handle tasks like selecting a WAF provider, configuring rulesets based on application needs, and integrating the WAF into existing infrastructure. This helps protect web applications from common attacks by filtering malicious traffic.
When to use it
- New Application Deployment: Automatically set up a WAF as part of the deployment process for new web applications.
- Security Audit Remediation: Quickly deploy or reconfigure WAFs to address vulnerabilities identified during security audits.
- Protecting Legacy Applications: Add WAF protection to older applications that lack built-in security features.
- Responding to Emerging Threats: Rapidly adjust WAF rulesets in response to newly discovered attack vectors.
Key capabilities
- WAF provider selection
- Ruleset configuration based on application needs
- Integration with existing infrastructure
- Automated deployment
Example prompts
- "Deploy a ModSecurity WAF for my e-commerce site."
- "Configure the AWS WAF to block requests from known malicious IP addresses."
- “Set up a Cloudflare WAF and enable the standard ruleset.”
Tips & gotchas
The skill requires knowledge of your application's architecture and security requirements. Incorrectly configured WAF rules can inadvertently block legitimate traffic, so thorough testing is recommended after deployment.