Skip to content
SkillModel-led3,769 tokens in use

security-and-hardening

Harden code with threat modeling, a three-tier boundary system, OWASP controls and supply-chain, privacy and LLM guidance.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/security-and-hardening
npx skills add addyosmani/agent-skills --skill security-and-hardening
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing security-and-hardening costs

117tokens idle
3,769tokens in use
6,948tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples3/15
  • Output15/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Security and Hardening treats every external input as hostile and starts each feature with a short threat model: map trust boundaries, name assets, apply STRIDE and write abuse cases. A three-tier boundary system lists what to always do, what needs human approval and what never to do.

The skill covers injection, XSS, access control, authentication and sessions, headers and CORS, input validation, uploads, SSRF, destructive operations on derived paths, rate limiting, secrets, dependency audits, personal data and LLM output. Worked code sits in a references file.

What You Get

  • A threat modeling process with a STRIDE table
  • Always do, ask first and never do boundary lists
  • Control guidance for the OWASP classes, SSRF, rate limiting and secrets
  • A references file of code patterns, a red flag list and a verification checklist

Common Use Cases

  • Handling user input and authentication
  • Reviewing a feature that fetches user-supplied URLs
  • Auditing dependencies and supply-chain risk
  • Adding AI features or collecting personal data

What Makes It Unique

Besides the usual OWASP controls, the skill includes a rule for destructive operations on derived paths, with allowlisted root, minimum depth and ownership evidence, plus dependency steps that block install scripts and judge reachability. It also covers privacy duties and the OWASP list for LLM applications.

Under The Hood

The SKILL.md is the workflow and a references file holds TypeScript patterns. The skill runs no scripts of its own. It tells the agent to run package-manager audits, git diff checks for secrets and install-script policies, which reach package registries, and to read a shared security checklist in the repository.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers