Skip to main content
skill CX Codex

application-security · oakoss — Claude Code skill: OWASP Top 10, STRIDE

application-security walks your code and design through OWASP Top 10 and STRIDE, then hands over a pre-deploy checklist plus the compliance angles for GDPR, HIPAA, SOC 2 and PCI-DSS.

MIT 287 installs ★ 29 updated 2026-08-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add oakoss/agent-skills --skill application-security -a claude-code
Open on GitHub

What application-security does

The skill is a reference an agent reads before it touches auth, APIs or data flows. It carries the OWASP Top 10 list as of 2025, the API Security Top 10 from 2023, baseline principles such as least privilege and zero trust, and a checklist to run through before deployment that names concrete settings: argon2id for stored passwords, short-lived access tokens, HttpOnly cookies, restrictive CORS.

Threat modelling gets its own STRIDE table with mitigations per category, plus risk levels from critical down to low. Compliance is summarised for GDPR, HIPAA, SOC 2 and PCI-DSS, with what each framework asks of the code.

It ships as a single SKILL.md dropped into your agent's skills directory. There is no slash command to type — user-invocable: false means the agent pulls it in when a request looks like a security review, an auth setup or audit prep. The checklist sets the bar; it runs nothing. SBOM generation, npm audit and Dependabot sit in it as items you still execute yourself.

What it helps with

  • audit a fresh endpoint against OWASP Top 10
  • draft a STRIDE threat model for a file upload feature
  • pick JWT signing algorithm and token lifetimes
  • turn GDPR and HIPAA duties into concrete tickets
  • spot permission checks that live only in the browser

Example prompts for the agent

  • Check src/api/orders.ts for OWASP Top 10 issues and tell me what to fix first.
  • Build a STRIDE threat model for the file upload service.
  • Which security headers and CSP nonce should I set in next.config.js?

How to install application-security

1Skills CLI (Vercel)

npx skills add oakoss/agent-skills --skill application-security -a claude-code

2Manually: put the files in place

~/.claude/skills/application-security/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/application-security/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about application-security

How do I install application-security in Claude Code?

Run npx skills add oakoss/agent-skills --skill application-security -a claude-code. The skill lands at ~/.claude/skills/application-security/SKILL.md.

What does application-security do?

It gives the agent OWASP Top 10 (2025) and OWASP API Security Top 10 (2023) tables, core security principles, a pre-deploy checklist, a STRIDE threat model and a summary of GDPR, HIPAA, SOC 2 and PCI-DSS requirements.

Why is there no slash command for it?

Its metadata sets user-invocable: false, so you cannot call it by hand. The agent loads the skill when a request matches the description, for example a code review for vulnerabilities or setting up auth.

Source text

SKILL.md · MIT
---
name: application-security
description: 'Application security covering threat modeling (STRIDE), OWASP Top 10 (2025), OWASP API Security Top 10 (2023), secure coding review, authentication/authorization patterns, input validation, encryption, security headers, supply chain security, compliance (GDPR/HIPAA/SOC2/PCI-DSS), and security monitoring. Use when reviewing code for vulnerabilities, implementing auth patterns, securing APIs, configuring security headers, hardening supply chain, preventing injection attacks, or preparing for compliance audits.'
license: MIT
metadata:
  author: oakoss
  version: '1.1'
user-invocable: false
---

# Security

Security is built-in, not bolted-on. Every feature, endpoint, and data flow must consider security implications.

## OWASP Top 10 (2025)

| #   | Vulnerability                      | Prevention                                      |
| --- | ---------------------------------- | ----------------------------------------------- |
| 1   | Broken Access Control              | Verify permissions server-side, default deny    |
| 2   | Security Misconfiguration          | Secure defaults, remove unused features         |
| 3   | Software Supply Chain Failures     | SBOM, dependency scanning, signed builds        |
| 4   | Cryptographic Failures             | Use TLS, hash passwords (argon2id), encrypt PII |
| 5   | Injection                          | Parameterized queries, input validation         |
| 6   | Insecure Design                    | Threat modeling, security requirements          |
| 7   | Authentication Failures            | Strong passwords, MFA, secure session mgmt      |
| 8   | Software or Data Integrity         | Verify dependencies, sign releases              |
| 9   | Logging and Alerting Failures      | Log security events, set up alerts              |
| 10  | Mishandling Exceptional Conditions | Fail securely, generic errors to clients        |

## Security Principles

| Principle          | Rule                                                      |
| ------------------ | --------------------------------------------------------- |
| Defense in Depth   | Multiple layers: firewall, auth, authz, encryption, audit |
| Least Privilege    | Minimum permissions needed, nothing more                  |
| Zero Trust         | Never trust, always verify. Assume breach.                |
| Secure by Default  | HTTPS, strict passwords, secure cookies out of the box    |
| Fail Securely      | Access denied on error, no internal details to users      |
| Validate on Server | Client validation is UX, server validation is security    |

## Pre-Deployment Checklist

| Area          | Requirements                                                        |
| ------------- | ------------------------------------------------------------------- |
| Passwords     | Hashed with argon2id (preferred) or bcrypt (12+ rounds)             |
| Tokens        | JWT with EdDSA/ES256, 15min access / 7d refresh, httpOnly cookies   |
| Sessions      | HttpOnly, Secure, SameSite=Strict cookies                           |
| Rate Limiting | Auth endpoints: 5 attempts/15min                                    |
| Authorization | All routes check auth server-side, default deny                     |
| Input         | Validated with schema (Zod), parameterized SQL                      |
| Uploads       | Whitelist types, enforce size limits                                |
| Secrets       | No secrets in code or VCS                                           |
| Headers       | CSP (with nonces), HSTS, Permissions-Policy, X-Content-Type-Options |
| CORS          | Configured restrictively                                            |
| Encryption    | PII encrypted at rest (AES-256) and in transit (TLS 1.3)            |
| Logging       | Audit logging for security events                                   |
| Dependencies  | SBOM generated, `npm audit` clean, Dependabot enabled               |

## Threat Modeling (STRIDE)

| Threat                 | Category        | Key Mitigations                                        |
| ---------------------- | --------------- | ------------------------------------------------------ |
| Spoofing               | Authentication  | MFA, strong passwords, JWT with short expiry           |
| Tampering              | Integrity       | Input validation, HTTPS/TLS, signed tokens             |
| Repudiation            | Accountability  | Audit logging, digital signatures                      |
| Info Disclosure        | Confidentiality | Encryption, least privilege, secret management         |
| Denial of Service      | Availability    | Rate limiting, input validation, CDN/DDoS protection   |
| Elevation of Privilege | Authorization   | Authz checks on every request, ABAC, permission audits |

## Risk Levels

| Level    | Action                    |
| -------- | ------------------------- |
| Critical | Immediate action required |
| High     | Address before launch     |
| Medium   | Address post-launch       |
| Low      | Monitor, may accept risk  |

## Compliance Overview

| Framework | Scope              | Key Requirements                                                   |
| --------- | ------------------ | ------------------------------------------------------------------ |
| GDPR      | EU data subjects   | Consent, data subject rights, breach notification (72h), DPIA      |
| HIPAA     | US healthcare data | PHI encryption, RBAC, audit logs, BAA with providers               |
| SOC 2     | SaaS customer data | Security policies, MFA, encryption, incident response              |
| PCI-DSS   | Credit card data   | Use payment processor (Stripe), tokenization, network segmentation |

## Anti-Patterns

| Anti-Pattern                                  | Fix                                              |
| --------------------------------------------- | ------------------------------------------------ |
| Security as afterthought                      | Integrate from design phase                      |
| Client-side authorization                     | Always verify permissions server-side            |
| Trusting client data (e.g., userId from body) | Get user ID from authenticated session           |
| Rolling your own crypto                       | Use proven libraries (argon2, bcrypt, libsodium) |
| Compliance = security                         | Compliance is the minimum; security is ongoing   |
| Verbose error responses                       | Generic messages to clients, details server-side |

## Common Mistakes

| Mistake                                                       | Correct Pattern                                                     |
| ------------------------------------------------------------- | ------------------------------------------------------------------- |
| Performing authorization checks only on the client side       | Always verify permissions server-side; client checks are UX only    |
| Trusting user-supplied IDs from request body (e.g., userId)   | Derive user identity from the authenticated session or token        |
| Rolling custom cryptography instead of using proven libraries | Use argon2id, bcrypt, or libsodium for all cryptographic operations |
| Treating compliance certification as equivalent to security   | Compliance is the minimum bar; security requires ongoing review     |
| Returning verbose error messages with stack traces to clients | Show generic messages to clients; log details server-side only      |

## Delegation

- **Scan codebase for OWASP Top 10 vulnerabilities and insecure patterns**: Use `Explore` agent to search for SQL injection, XSS, and hardcoded secrets
- **Implement authentication, authorization, and security headers end-to-end**: Use `Task` agent to configure JWT, RBAC, CSP, HSTS, and rate limiting
- **Design a threat model and security architecture for new features**: Use `Plan` agent to apply STRIDE methodology and map trust boundaries

> For database-layer security (RLS policies, Postgres/Supabase hardening, audit trails), use the `database-security` skill. For AI/LLM security (prompt injection defense, agentic zero-trust, MCP tool hardening), use the `secure-ai` skill.

## References

- [Threat Modeling](references/threat-modeling.md) — STRIDE methodology, risk assessment process, trust boundaries
- [Authentication and Authorization](references/auth.md) — JWT, session-based, OAuth, RBAC, ABAC, IDOR protection
- [API Security](references/api-security.md) — OWASP API Security Top 10, object-level authorization, rate limiting, SSRF prevention, security testing
- [Input Validation](references/input-validation.md) — SQL injection, XSS, command injection, path traversal, Zod validation, file upload security
- [Data Protection](references/data-protection.md) — Password hashing (argon2id/bcrypt), AES-256-GCM encryption, secrets management
- [Secure Configuration](references/secure-config.md) — Security headers, CORS, Express hardening, rate limiting
- [Supply Chain Security](references/supply-chain.md) — SBOM generation, dependency scanning, CI/CD hardening, artifact signing
- [Monitoring and Compliance](references/monitoring-compliance.md) — Audit logging, error handling, GDPR/HIPAA/SOC2/PCI-DSS, troubleshooting

© oakoss · MIT · oakoss/agent-skills

Similar skills

All skills for Security →

application-security by other authors comes first.

application-security travisjneuman application-security is a Claude Code skill for hardening web apps and reviewing security risks. It activates for code reviews, vulnerability checks, and defensive implementation work. CX Codex +1 181installs Security Architect daffy0208 Security Architect evaluates system designs with STRIDE threat modeling, checks code against OWASP flaws, and validates regulatory standards. CX Codex +1 175installs engineering-security-engineer PeterHdd engineering-security-engineer — a skill for Claude Code guides application security reviews, threat modeling, and infrastructure hardening. It handles OWASP Top 10 remediation, credential leak audits, and authorization checks. CX Codex +1 639installs security-pentest-planner OneWave-AI security-pentest-planner builds a penetration test plan for web applications: analyzes code, API routes, authentication and infrastructure configs, generates pentest-plan.md with concrete test cases. CX Codex +1 297installs security-assessment Rudolf S. security-assessment — a Claude skill that runs a security audit: STRIDE threat modelling, OWASP-based code review, and findings ranked by severity with fixes. CX Codex +1 ★ 587repo stars sparkfinderoven-security-compliance-suite reason-machines sparkfinderoven-security-compliance-suite automates OWASP vulnerability checks, dependency CVE scans, and SOC2 or GDPR audits inside your development workflow. Designed for security assessments during coding. CX Codex +1 725installs api-security-best-practices davila7 api-security-best-practices is a Claude Code skill for API security design. It applies when building endpoints, reviewing existing APIs, or adding authentication and access controls. CX Codex +1 1,739installs

From the same set106

The whole set →

Project sponsors

Companies that keep this analytics open