Skip to content
TrustedSkillsbeta
Back to all skills

Owasp Security Check

Checked
sergiodxa·vlatest·security·MIT

Identifies potential OWASP Top 10 vulnerabilities in web applications based on provided code or URLs.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sergiodxa/agent-skills --skill owasp-security-check -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sergiodxa

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sergiodxa/agent-skills at 40e21b4618.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
40e21b4618
Manifest
skills/owasp-security-check/SKILL.md
Scanned
21 files, 2,804 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The owasp-security-check skill performs security assessments based on OWASP guidelines, identifying vulnerabilities such as injection flaws, broken authentication, and insecure APIs in web applications. It automates checks for common security issues using predefined rules and best practices from the Open Web Application Security Project (OWASP).

When to use it

  • Before deploying a new web application to identify potential security risks.
  • During routine security audits of existing systems.
  • When integrating third-party APIs or libraries into an application.
  • As part of a CI/CD pipeline to enforce security standards automatically.

Key capabilities

  • Scans for OWASP Top 10 vulnerabilities.
  • Analyzes code and configurations for insecure practices.
  • Provides actionable remediation suggestions.
  • Integrates with development workflows for automated testing.

Example prompts

  • "Run an OWASP security check on my web application."
  • "Check this API endpoint for common vulnerabilities using OWASP guidelines."
  • "Scan the latest commit in my repository for security issues."

Tips & gotchas

  • Ensure your codebase is up to date before running the scan for accurate results.
  • The skill may require access to source code or configuration files, so permissions must be properly set.