security-and-hardening

We split this skill into the rules it gives an agent

3 rules. 1 is common, 1 is distinctive, and 1 is very specific to this project.

• 1

  Common

  Most of the 79 edited versions we read keep these.

• 1

  Distinctive

  This author's own choices. Worth a look.

• 1

  Very specific

  Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — 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 79 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.

• Other versions84 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 17

  1. shashankswe2020-ux/whoop-mcp★ 17411% same
  2. jmxt3/gitscape.ai★ 3311% same
  3. sampleXbro/agentsmesh★ 2411% same
  4. lza6/claw-code-tingfeng★ 511% same
  5. Envy-7z/katalyst★ 411% same
  6. SrejonKhan/agent-skills★ 311% same
  7. huangzida/skills★ 211% same
  8. Minghou-Lei/codex-skills★ 211% same
  9. Puen2001/aether-os★ 211% same
  10. skytiger6724/qwen-skills★ 211% same

  7 more not listed

  Wrote their own version · 67

  1. addyosmani/agent-skills★ 112ksame name
  2. penpot/penpot★ 62ksame name
  3. ollaya-dev/ollaya★ 1.4ksame name
  4. rizqinrr/viserys-agent★ 560same name
  5. vinvcn/addyosmani-agent-skills-zh★ 46same name
  6. jaskirat1616/grok-skills★ 22same name
  7. JPeetz/agent-skills★ 14same name
  8. moberghr/mtk-agent-toolkit★ 9same name
  9. HK-hub/AgentSkills★ 6same name
  10. coreplanelabs/switchboard★ 5same name

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

• Used alongsideProjects with it also use constraint-driven-development, observability-and-instrumentation and 5 more.

  Other files people use alongside this one.

  How we pick theseFiles 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 17 projects that use this

  • HK-hubSkill

    observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

    Also in 35 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

  • OpenAISkill

    verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    Also in 9 projects that use this

  • OpenAISkill

    using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    Also in 5 projects that use this

  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 5 projects that use this

• In this repository29 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • api-and-interface-designSkill
  • ci-cd-and-automationSkill
  • code-review-and-qualitySkill
  • code-simplificationSkill
  • context-engineeringSkill
  • debugging-and-error-recoverySkill
  • deprecation-and-migrationSkill
  • documentation-and-adrsSkill
  • doubt-driven-developmentSkill
  • git-workflow-and-versioningSkill
  • idea-refineSkill
  • incremental-implementationSkill
  • interview-meSkill
  • performance-optimizationSkill
  • planning-and-task-breakdownSkill
  • shipping-and-launchSkill
  • source-driven-developmentSkill
  • spec-driven-developmentSkill
  • test-driven-developmentSkill
  • using-agent-skillsSkill
  • zynk-pre-release-auditSkill
  • debugging-difficult-bugsSkill
  • pr-explainerSkill
  • pr-splitterSkill
  • smoke-testSkill
  • zynk-docsSkill
  • zynkSkill