code-security

semgrep/skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/semgrep/skills --skill code-security
0 commentsdiscussion
summary

Comprehensive security rules for writing secure code across 15+ languages. Covers OWASP Top 10, infrastructure security, and coding best practices with 28 rule categories.

skill.md

Code Security Guidelines

Comprehensive security rules for writing secure code across 15+ languages. Covers OWASP Top 10, infrastructure security, and coding best practices with 28 rule categories.

How to Use This Skill

Proactive mode — When writing or reviewing code, automatically check for relevant vulnerabilities based on the language and patterns present. You don't need to wait for the user to ask about security.

Reactive mode — When the user asks about security, use the categories below to find the relevant rule file, then read it for detailed vulnerable/secure code examples.

Workflow

  1. Identify the language and what the code does (handles input? queries a DB? reads files?)
  2. Check the relevant rules below — focus on Critical and High impact first
  3. Read the specific rule file from rules/ for detailed code examples in that language
  4. Apply the secure patterns, or flag the vulnerable patterns if reviewing

Language-Specific Priority Rules

When writing code in these languages, check these rules first:

Language Priority Rules to Check
Python SQL injection, command injection, path traversal, code injection, SSRF, insecure crypto
JavaScript/TypeScript XSS, prototype pollution, code injection, insecure transport, CSRF
Java SQL injection, XXE, insecure deserialization, insecure crypto, SSRF
Go SQL injection, command injection, path traversal, insecure transport
C/C++ Memory safety, unsafe functions, command injection, path traversal
Ruby SQL injection, command injection, code injection, insecure deserialization
PHP SQL injection, XSS, command injection, code injection, path traversal
HCL/YAML Terraform (AWS/Azure/GCP), Kubernetes, Docker, GitHub Actions

Categories

Critical Impact

  • SQL Injection (rules/sql-injection.md) - Use parameterized queries, never concatenate user input
  • Command Injection (rules/command-injection.md) - Avoid shell commands with user input, use safe APIs
  • XSS (rules/xss.md) - Escape output, use framework protections
  • XXE (rules/xxe.md) - Disable external entities in XML parsers
  • Path Traversal (rules/path-traversal.md) - Validate and sanitize file paths
  • Insecure Deserialization (rules/insecure-deserialization.md) - Never deserialize untrusted data
  • Code Injection (rules/code-injection.md) - Never eval() user input
  • Hardcoded Secrets (rules/secrets.md) - Use environment variables or secret managers
  • Memory Safety (rules/memory-safety.md) - Prevent buffer overflows, use-after-free (C/C++)

High Impact

  • Insecure Crypto (rules/insecure-crypto.md) - Use SHA-256+, AES-256, avoid MD5/SHA1/DES
  • Insecure Transport (rules/insecure-transport.md) - Use HTTPS, verify certificates
  • SSRF (rules/ssrf.md) - Validate URLs, use allowlists
  • JWT Issues (rules/authentication-jwt.md) - Always verify signatures
  • CSRF (rules/csrf.md) - Use CSRF tokens on state-changing requests
  • Prototype Pollution (rules/prototype-pollution.md) - Validate object keys in JavaScript

Infrastructure

  • Terraform AWS/Azure/GCP (rules/terraform-aws.md, rules/terraform-azure.md, rules/terraform-gcp.md) - Encryption, least privilege, no public access
  • Kubernetes (rules/kubernetes.md) - No privileged containers, run as non-root
  • Docker (rules/docker.md) - Don't run as root, pin image versions
  • GitHub Actions (rules/github-actions.md) - Avoid script injection, pin action versions

Medium/Low Impact

  • Regex DoS (rules/regex-dos.md) - Avoid catastrophic backtracking
  • Race Conditions (rules/race-condition.md) - Use proper synchronization
  • Correctness (rules/correctness.md) - Avoid common logic bugs
  • Best Practices (rules/best-practice.md) - General secure coding patterns

See rules/_sections.md for the full index with CWE/OWASP references.

Quick Reference

Vulnerability Key Prevention
SQL Injection Parameterized queries
XSS Output encoding
Command Injection Avoid shell, use APIs
Path Traversal Validate paths
SSRF URL allowlists
Secrets Environment variables
Crypto SHA-256, AES-256
how to use code-security

How to use code-security on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add code-security
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/semgrep/skills --skill code-security

The skills CLI fetches code-security from GitHub repository semgrep/skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/code-security

Reload or restart Cursor to activate code-security. Access the skill through slash commands (e.g., /code-security) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.648 reviews
  • Arjun Srinivasan· Dec 24, 2024

    code-security reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Min Ndlovu· Dec 24, 2024

    code-security fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Dec 12, 2024

    code-security has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Carlos Chen· Dec 8, 2024

    We added code-security from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sakura Anderson· Nov 27, 2024

    Keeps context tight: code-security is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Arya Malhotra· Nov 15, 2024

    Registry listing for code-security matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kwame Park· Nov 15, 2024

    I recommend code-security for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Camila Choi· Nov 7, 2024

    code-security is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yash Thakker· Nov 3, 2024

    Solid pick for teams standardizing on skills: code-security is focused, and the summary matches what you get after install.

  • Soo Mehta· Oct 26, 2024

    Useful defaults in code-security — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 48

1 / 5