security-and-hardening
Skill0 starsChanged 3 months agoMITView on GitHub
Use when handling user input, auth, secrets, or external integrations — prevent OWASP Top 10, enforce auth patterns, secrets management, and dependency auditing.
92 other projects use a version of this.
Adopted by
Most recently taken up by
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- Alter-ai/skill-labtheir own version, first seen Nov 15, 2026
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- tkbk-online/skillstheir own version, first seen Nov 15, 2026
- ontology-of-everything/handy-skillstheir own version, first seen Nov 15, 2026
- slantview/pi-agentstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use constraint-driven-development, deprecation-and-migration and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 16 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 40 projects that use this
HK-hubSkillcode-simplification
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Also in 51 projects that use this
jarosser06Skilltest-strategy
Plans pytest test strategies for Drift's 90%+ coverage requirement using coverage analysis, edge case identification, and test suite design. Use when determining what tests to write, analyzing coverage gaps, or planning test strategies.
Also in 3 projects that use this
silvainfmSkillmarketing-ideas
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 140 proven marketing approaches organized by category.
Also in 3 projects that use this
Other versions92 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 92
- addyosmani/agent-skills★ 118ksame name
- penpot/penpot★ 62ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- shashankswe2020-ux/whoop-mcp★ 181same name
- enes-alatas/spool★ 48same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
- jmxt3/gitscape.ai★ 33same name
- sampleXbro/agentsmesh★ 27same name
- jaskirat1616/grok-skills★ 22same name
- ishandutta2007/Awesome-Agent-Skills★ 21same name
82 more not listed
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 repository64 other files it gives its agents.
- subagent-driven-developmentSkill
- crazy-skills-catalogSkill
- frontend-designSkill
- system-architectureSkill
- git-workflow-and-versioningSkill
- using-git-worktreesSkill
- documentation-and-adrsSkill
- readme-generationSkill
- accessibilitySkill
- adverse-reviewSkill
- aeoSkill
- agent-designerSkill
- api-and-interface-designSkill
- best-practicesSkill
- browser-testing-with-devtoolsSkill
- canvas-designSkill
- ceo-advisorSkill
- ci-cd-and-automationSkill
- content-creatorSkill
- context-engineeringSkill
- create-voltagentSkill
- cto-advisorSkill
- deep-researchSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- gdprSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- iso27001Skill
- local-seo-managerSkill
- mcp-server-builderSkill
- observability-and-instrumentationSkill
- performanceSkill
- planning-and-task-breakdownSkill
- product-manager-toolkitSkill
- research-orchestratorSkill
- saas-metrics-coachSkill
- seoSkill
- soc2Skill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- tech-debt-trackerSkill
- voltagent-best-practicesSkill
- voltagent-core-referenceSkill
- voltagent-docs-bundleSkill
- web-quality-auditSkill
- using-crazy-skillsSkill
- writing-skillsSkill
- core-web-vitalsSkill
- performance-optimizationSkill
- context-compressionSkill
- prompt-enhancementSkill
- token-efficiencySkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- verification-before-completionSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- brainstormingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 87 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before merging changes that add dependencies or expose endpoints
- Distinctive: line 14
When auditing for secrets or CVEs
“Common” is measured: kept by at least 6 in 10 of the 87 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.
Files
Security and Hardening
OWASP Top 10 prevention and hardening. Composite of addyosmani/agent-skills security-and-hardening + alirezarezvani/claude-code-tresor secret-scanner/dependency-auditor + trailofbits/skills.
When to use
- Any code touching user input, authentication, data storage, or external APIs
- Before merging changes that add dependencies or expose endpoints
- When auditing for secrets or CVEs
Workflow
- Identify boundaries — Classify trust boundaries (user → app → DB → external). Apply three-tier boundary system: validate at entry, sanitize at use, escape at output.
- Check OWASP Top 10 — For this change, verify:
- Injection (SQL, XSS, command) — parameterized queries, escaping
- Broken auth — JWT expiry, refresh, rate limit
- Secrets — no hardcoded keys,
secret-scannerpre-commit - Dependencies —
dependency-auditorfor CVEs, license compliance
- Apply fixes — One fix per boundary, add failing test that demonstrates the vulnerability before fixing.
- Verify — Re-run scanners, ensure 0 highs, add regression test that would fail if vulnerability returned.
Verification
- Trust boundaries listed and each validated
- OWASP Top 10 checklist for this change has no open Highs
- Secret scan passes (no keys in diff), dependency audit passes or has plan
- Regression test for the vulnerability exists and passes
References
- Source:
addyosmani/agent-skillssecurity-and-hardening,alirezarezvani/claude-code-tresorsecurity/*,trailofbits/skills
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.

