Individual skill

sast-dast-pro

Run static and dynamic application security testing — tool selection, tuning, triage, and developer integration.

skills/sast-dast-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

SAST (static analysis — examining code without running it) and DAST (dynamic analysis — testing the running application) are complementary: SAST finds code-level flaws early and cheaply across the whole codebase; DAST finds runtime issues — auth flaws, misconfigurations, injection in context — that static analysis cannot see. Mature programs run both, tuned, with developers in the loop.

This skill covers operating both well: tool selection, rule tuning, triage workflows, and integration into development without destroying velocity.

Tune for the developer's trust, not the scanner's ego: a SAST rule that fires 500 false positives will get the whole tool ignored, including the 5 true positives. Ruthlessly disable noisy rules, write custom rules for your frameworks' dangerous patterns, and measure precision like your program depends on it — because it does.

## When to use

- Selecting and deploying SAST/DAST tooling for the first time.
- Tuning noisy tools that developers have started ignoring.
- Building triage workflows (security review of findings, developer fix loop).
- Adding custom rules for framework-specific dangerous patterns.