Workers Security
ListedProactively identifies and mitigates worker safety risks using real-time data analysis and predictive modeling.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
cloudflare-workers-security, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add secondsky/claude-skills --skill cloudflare-workers-security -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
secondsky
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: evil.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
127.0.0.1localevil.comundeclaredWhat it found
- plugins/cloudflare-workers/skills/cloudflare-workers-security/scripts/security-audit.sh:309contacts evil.com
-H "Origin: https://evil.com" \ - plugins/cloudflare-workers/skills/cloudflare-workers-security/scripts/security-audit.sh:316contacts evil.com
elif [ "$acao" = "https://evil.com" ]; then
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 secondsky/claude-skills at 8837836131.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8837836131
- Scanned
- 12 files, 5,081 lines
About this skill
What it does
This skill enables AI agents to interact with Cloudflare Workers security features, allowing them to inspect and manage worker configurations related to protection mechanisms. It facilitates direct control over security policies within the Cloudflare environment through programmatic access.
When to use it
- Automating the deployment of security updates across multiple Cloudflare Workers instances.
- Dynamically adjusting rate limiting rules based on real-time traffic analysis.
- Integrating security validation checks into CI/CD pipelines for worker deployments.
- Responding to security alerts by programmatically modifying worker protection settings.
Key capabilities
- Access and modify Cloudflare Workers security configurations.
- Manage rate limiting policies directly from the agent.
- Inspect current security status of deployed workers.
- Execute security-related commands within the Cloudflare ecosystem.
Example prompts
- "Update the rate limit for my 'api-worker' to 100 requests per minute."
- "Check if any security vulnerabilities are detected in my active Workers."
- "Enable bot protection on all my deployed Cloudflare Workers."
Tips & gotchas
Ensure you have appropriate API credentials and permissions before attempting to modify security settings, as unauthorized changes can disrupt service availability. Always test security rule changes in a staging environment first to prevent unintended blocking of legitimate traffic.