Skip to content
TrustedSkillsbeta
Back to all skills

Owasp Security

Listed
agamm·vlatest·security·MIT

Identifies OWASP Top 10 vulnerabilities in code and configurations based on agamm's secure development practices.

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 agamm/claude-code-owasp --skill owasp-security -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

agamm

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: xml.org.

    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.

    Hosts contacted

    xml.orgundeclared

    What it found

    • .claude/skills/owasp-security/reference/languages.md:254contacts xml.org
      factory.setFeature("http://xml.org/sax/features/external-general-entities", false)

  • 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 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 agamm/claude-code-owasp at 8ac7965caa.

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

Commit
8ac7965caa
Manifest
.claude/skills/owasp-security/SKILL.md
Scanned
5 files, 2,097 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

The OWASP Security skill enables AI agents to apply security best practices and guidelines from the Open Web Application Security Project (OWASP) during code generation, review, and auditing tasks. It ensures that software development aligns with industry-standard threat modeling and vulnerability mitigation strategies.

When to use it

  • Reviewing generated code for common vulnerabilities like SQL injection or cross-site scripting before deployment.
  • Generating secure boilerplate code that adheres to OWASP Top 10 recommendations from the start.
  • Auditing existing application logic to identify missing security controls or weak authentication mechanisms.
  • Creating documentation on secure coding practices tailored to specific frameworks or languages.

Key capabilities

  • Integration of OWASP guidelines into AI-driven development workflows.
  • Identification and remediation of standard web application security risks.
  • Generation of secure code patterns aligned with recognized security standards.

Example prompts

  • "Generate a Python Flask API endpoint that handles user login securely, following OWASP authentication guidelines."
  • "Review this JavaScript snippet for potential cross-site scripting (XSS) vulnerabilities and suggest fixes based on OWASP recommendations."
  • "Create a checklist for securing a RESTful API against common threats outlined in the OWASP Top 10."

Tips & gotchas

Ensure your AI agent has access to up-to-date OWASP documentation, as standards evolve frequently. This skill complements but does not replace manual security testing or penetration testing by human experts.