security-guardian
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Act as a security and firewall administrator to audit, validate, and protect all code, skills, artifacts, and modules generated in this workspace. Use this skill whenever: (1) a new skill is being created or updated, (2) any code, artifact, React component, HTML file, or script is being generated, (3) API keys, environment variables, tokens, secrets, or credentials are mentioned or appear in any content, (4) firewall rules or network configurations are being designed, (5) the user asks for a security check, security review, vulnerability scan, or audit of any content. Also trigger automatically when cross-referencing multiple skills or modules for consistency — security must be verified even if the user doesn't explicitly ask. Do NOT skip this skill when generating code "just as an example" or "for demo purposes" — insecure demo code is still insecure.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- rtk-ai/rtktheir own version, first seen Oct 13, 2026
- Hacck3y/ptktheir own version, first seen Oct 8, 2026
- FlorianBruniaux/ccboardtheir own version, first seen Apr 29, 2026
- ufodev-io/claude-skillstheir own version, first seen Apr 7, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- rtk-ai/rtk★ 86ksame name
- FlorianBruniaux/ccboard★ 94same name
- Hacck3y/ptk★ 2same name
- ufodev-io/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- cyber-securitySkill
- dev-protocolSkill
- digital-marketing-proSkill
- email-ops-domain-knowledgeSkill
- fullstack-developerSkill
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-guideSkill
- gitnexus-impact-analysisSkill
- gitnexus-pr-reviewSkill
- gitnexus-refactoringSkill
- ops-managerSkill
- senior-dev-modeSkill
- superpowers-brainstormingSkill
- superpowers-debuggingSkill
- superpowers-tddSkill
- superpowers-writing-plansSkill
- terraSkill
- ui-ux-pro-maxSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.