3.2 KiB
SAST Security Assessment
Your goal is to identify security vulnerabilities in the codebase located in the current directory.
Step 1: Codebase Analysis & Threat Modeling
Before running, check if sast/architecture.md already exists. If it does, skip this step.
Run the sast-analysis skill directly (this one stays in-session since later steps depend on reading its output).
Wait for this step to finish before proceeding.
Step 2: Vulnerability Detection (Parallel)
Run all checks at the same time. Skip any task where the output file already exists.
- Skip IDOR if
sast/idor-results.mdalready exists. - Skip SQLi if
sast/sqli-results.mdalready exists. - Skip SSRF if
sast/ssrf-results.mdalready exists. - Skip XSS if
sast/xss-results.mdalready exists. - Skip RCE if
sast/rce-results.mdalready exists. - Skip XXE if
sast/xxe-results.mdalready exists. - Skip File Upload if
sast/fileupload-results.mdalready exists. - Skip Path Traversal if
sast/pathtraversal-results.mdalready exists. - Skip SSTI if
sast/ssti-results.mdalready exists. - Skip JWT if
sast/jwt-results.mdalready exists. - Skip Missing Auth if
sast/missingauth-results.mdalready exists. - Skip Business Logic if
sast/businesslogic-results.mdalready exists. - Skip GraphQL injection if
sast/graphql-results.mdalready exists.
Start one subagent per check, all in parallel, each with a dedicated task. Give each subagent the same instruction pattern, using the skill name and paths from the table:
Read
sast/architecture.mdfor context, then run the named SAST skill. Write all findings to that skill's results file. Clean up any intermediate recon or threat files for that skill when done.
| Skill | Results file | Typical intermediate files to clean |
|---|---|---|
| sast-idor | sast/idor-results.md |
sast/idor-recon.md |
| sast-sqli | sast/sqli-results.md |
sast/sqli-recon.md |
| sast-ssrf | sast/ssrf-results.md |
sast/ssrf-recon.md |
| sast-xss | sast/xss-results.md |
sast/xss-recon.md |
| sast-rce | sast/rce-results.md |
sast/rce-recon.md |
| sast-xxe | sast/xxe-results.md |
sast/xxe-recon.md |
| sast-fileupload | sast/fileupload-results.md |
sast/fileupload-recon.md |
| sast-pathtraversal | sast/pathtraversal-results.md |
sast/pathtraversal-recon.md |
| sast-ssti | sast/ssti-results.md |
sast/ssti-recon.md |
| sast-jwt | sast/jwt-results.md |
sast/jwt-recon.md |
| sast-missingauth | sast/missingauth-results.md |
sast/missingauth-recon.md |
| sast-businesslogic | sast/businesslogic-results.md |
sast/businesslogic-threats.md |
| sast-graphql | sast/graphql-results.md |
sast/graphql-recon.md |
Wait for all subagents to finish before proceeding.
Step 3: Report Generation
After all subagents from Step 2 finish, generate the final consolidated report.
Skip this step if sast/final-report.md already exists.
Launch a single subagent:
Read all available
sast/*-results.mdfiles andsast/architecture.mdfor context, then run the sast-report skill to generatesast/final-report.mdwith all findings ranked by severity and confidentiality impact.