Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Freebies — Basic Semgrep Linter

    1

    Run lightweight static analysis and OWASP security scans using sandboxed Semgrep runners.

    Free

    Security scanned
    Freebies — Basic Semgrep Linter

    Freebies — Basic Semgrep Linter

    Example session with this skill installed

    Run a basic Semgrep scan on the current project to find any High or Critical security vulnerabilities in the source code.

    • Read your context and instructions
    • Compiled the freebies

    I have inspected the workspace and generated a targeted Semgrep configuration to scan for high-risk patterns including hardcoded secrets, insecure TLS settings, and command injection vulnerabilities. The scan was executed via an ephemeral runner.

    Security Audit Findings

    SeverityVulnerability TypeFile PathLineDescription
    CRITICALHardcoded Secretsrc/config/db.js12Potential plaintext password assigned to DB_PASS.
    HIGHInsecure Commandscripts/deploy.py45Use of os.system() with unsanitized user input.
    HIGHWeak Cryptosrc/auth.ts89MD5 hash detected; use SHA-256 or higher for passwords.
    MEDIUMDebug Modeapp.py5Flask debug=True found in production-ready file.

    Summary: The scan identified 1 critical and 2 high-severity issues that require immediate attention.

    Next steps

    1. Move the hardcoded password in src/config/db.js to a .env file.
    2. Replace os.system() in scripts/deploy.py with the subprocess module using argument arrays.
    3. Update src/auth.ts to use a secure hashing algorithm like Argon2 or bcrypt.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Code audits often stall because setting up local security environments is a friction-heavy process. This skill eliminates that overhead by executing lightweight static analysis within your agent's sandbox using ephemeral runners. It identifies security antipatterns and OWASP vulnerabilities without requiring global package installations or elevated system privileges.

    What it does

    • Automated Source Inspection scans your repository workspace to identify target files for analysis.
    • YAML Pattern Generation creates standard Semgrep configuration files focused on common security flaws.
    • Sandboxed Execution runs scans through npx, pipx, or uvx to maintain environment isolation.
    • Severity Mapping categorizes findings into a Critical, High, Medium, and Low matrix.
    • Precise Location Reporting provides exact file paths and line numbers for every detected issue.

    How it works

    1. Analyze Workspace: The skill inspects the local directory to determine the language and project structure.
    2. Define Rules: It generates a .semgrep.yaml file containing patterns for common vulnerabilities like SQL injection or hardcoded secrets.
    3. Run Scan: It executes the linter using a project-scoped runner like npx semgrep.
    4. Report Findings: It parses the output into a structured severity matrix for immediate remediation.

    Frameworks & tools

    This tool uses Semgrep for static analysis and relies on project-scoped runners including npx, pipx, uvx, or venv. It is designed for DevSecOps workflows within sandboxed AI environments.

    Why this beats prompting it yourself

    Writing reliable Semgrep patterns manually is error-prone and time-consuming. This skill automates the configuration generation and ensures execution follows strict security guardrails, preventing the agent from attempting unauthorized global installs or privilege escalation.

    Use cases

    • Auditing pull requests for common OWASP Top 10 vulnerabilities.
    • Scanning for hardcoded credentials or API keys before a commit.
    • Running quick security checks in environments where you cannot install global tools.
    • Identifying deprecated or insecure function calls in legacy codebases.

    Known limitations

    Does not support cross-boundary taint analysis or deep data flow tracking. Analysis is strictly confined to the active project workspace and cannot access parent directories.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    No cross-boundary taint analysis. No global package installs or root access. Workspace restricted to current directory.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    • Free with an Agensi account

    Software
    semgrepNode.jsPython

    Permissions

    Read Files
    Listed4 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the configuration and execution of Semgrep within your agent's sandbox, eliminating the need for manual pattern writing or risky global package installations. It provides a structured security audit without the friction of setting up a local DevSecOps environment.

    The skill is compatible with any AI agent environment that supports sandboxed tool execution and has access to standard package runners like npx, pipx, or uvx. It is specifically designed to operate within confined workspaces without requiring elevated system privileges.

    The tool is optimized for common languages supported by Semgrep, such as Python, JavaScript, TypeScript, and Go. It automatically detects the project structure to apply the most relevant security patterns for those specific frameworks.

    No complex setup is required; the skill uses ephemeral runners to execute scans on-the-fly. As long as your agent has access to the project workspace and a package manager (like npm or pip), the linter will function immediately.

    You receive the full skill integration, including the automated YAML pattern generator, the workspace inspector, and the severity mapping logic. It also includes the necessary configurations to ensure the agent stays within security guardrails during execution.

    To maintain strict security and sandbox integrity, the analysis is confined to the active project directory. It cannot perform cross-boundary taint analysis or access files located in parent directories or external system paths.

    New in DevOps & Cloud

    Free