agentleFS
viasrijanviasrijan/crazy-skills/skills/security/security-and-hardening/SKILL.md

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

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.
  • MrCipherSmithSkill

    constraint-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-hubSkill

    deprecation-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-hubSkill

    code-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

  • jarosser06Skill

    test-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

  • silvainfmSkill

    marketing-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

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
  1. Distinctive:

    Before merging changes that add dependencies or expose endpoints

    line 13
  2. Distinctive:

    When auditing for secrets or CVEs

    line 14

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Identify boundaries — Classify trust boundaries (user → app → DB → external). Apply three-tier boundary system: validate at entry, sanitize at use, escape at output.
  2. 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-scanner pre-commit
    • Dependencies — dependency-auditor for CVEs, license compliance
  3. Apply fixes — One fix per boundary, add failing test that demonstrates the vulnerability before fixing.
  4. 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-skills security-and-hardening, alirezarezvani/claude-code-tresor security/*, trailofbits/skills

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.