Skip to content
TrustedSkillsbeta
Back to all skills

Dast Scanning

Checked
bagelhole·vlatest·security·MIT

Dast Scanning identifies vulnerabilities in your systems by analyzing open-source vulnerability databases – crucial for proactive security.

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 bagelhole/devops-security-agent-skills --skill dast-scanning -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

bagelhole

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 bagelhole/devops-security-agent-skills at 0365f57a07.

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

Commit
0365f57a07
Manifest
security/scanning/dast-scanning/SKILL.md
Scanned
2 files, 470 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

This skill performs Dynamic Application Security Testing (DAST) scans on web applications. It identifies vulnerabilities such as SQL injection, cross-site scripting (XSS), and other common security flaws by simulating real-world attacks against a running application. The results are then reported to highlight potential risks and areas for remediation.

When to use it

  • Pre-release testing: Scan an application before deployment to identify and fix vulnerabilities early in the development lifecycle.
  • Continuous Integration/Continuous Delivery (CI/CD) pipelines: Integrate DAST scanning into automated build processes to ensure ongoing security.
  • Post-deployment monitoring: Regularly scan live applications to detect new vulnerabilities introduced by code changes or external factors.
  • Security audits: Use DAST as part of a broader security audit process to assess the overall security posture of an application.

Key capabilities

  • Automated vulnerability scanning
  • Identification of common web application vulnerabilities (e.g., SQL injection, XSS)
  • Reporting of scan results with potential remediation guidance

Example prompts

  • "Scan this web application: https://example.com."
  • "Run a DAST scan on the staging environment at https://staging.example.com and report any high-severity findings."
  • "Perform a full DAST scan, including authentication flow testing, against https://internal.company.net."

Tips & gotchas

  • DAST scans require a running application to test; ensure the target environment is accessible and configured correctly.
  • Authentication flows can be complex; providing accurate credentials or configuration for authenticated scanning is crucial for comprehensive results.