菜单
Produces a SAST-FINDINGS.md (static security + secret findings over your OWN code, each reproduced, with remediation) after a blocking authorization+ownership check. Use to statically scan owned code for vulnerabilities and secrets, defensively.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sast-scan |
| description | Produces a SAST-FINDINGS.md (static security + secret findings over your OWN code, each reproduced, with remediation) after a blocking authorization+ownership check. Use to statically scan owned code for vulnerabilities and secrets, defensively. |
The static-analysis producer of the security-testing pack (D5, opt-in). It scans your own authorized
code for security weaknesses and committed secrets, reproduces each finding, and writes a
SAST-FINDINGS.md — findings paired with severity and remediation. It is defensive: the deliverable is a
findings-and-fix report over an asset you own, never a reusable exploit. Authorization plus ownership of the
code is the blocking precondition — no owned scope, no scan.
Findings verify by Audit (is each finding real, reproduced, traceable, remediable?). When no scanner binds, the scan degrades to a Review-mode manual pass and records the automated coverage as NOT-RUN — it never reports "clean" for a scan that did not run.
Does: confirm authorization + ownership first (blocking); resolve the security-scan capability through the
tool seam; run the scanner over the owned code; reproduce each candidate finding before reporting; redact
secrets in the report; write SAST-FINDINGS.md with severity + remediation owner per finding + stated
coverage; write a receipt. Does not: touch code it does not own or is not authorized for, report an
unreproduced candidate as a real finding, print a discovered secret in the clear, emit a reusable
exploit/payload, or claim clean coverage for an unrun scanner.
product-pentest; or to probe an AI model
— that is ai-red-team. This sub_target is static analysis over source.security-review.| Situation | Reference |
|---|---|
| Thin inputs / no scanner / weaponization ask | rules/cold-start.md |
| The scanner backend (capability resolution, degrade) | engine/tools/tool-resolve.py resolve security-scan |
| Per-sub_target must-declares · overlay · vocabulary | ../acceptance/sub-targets.md · ../acceptance/overlay.md · ../vocabulary.md |
| Sibling sub_targets (running app / AI model) | product-pentest · ai-red-team |
security-scan capability) and the finding classes in scope.../vocabulary.md, ../acceptance/) + state/intake.json.security-scan capability. If a scanner binds, run it
over the in-scope code. If none binds, degrade to a manual Review pass and mark the automated coverage
NOT-RUN — never fabricate "clean".SAST-FINDINGS.md — findings (reproduced) + remediation + coverage; hypotheses listed apart.A gate failure is fixed before lock, not waived — these mirror the authorization/security/testing gates.
security-test/SAST-FINDINGS.md if that dir exists) —
persistence: Spec-Anchored. Authorized scope · findings (reproduced, severity, remediation owner) ·
redacted secrets · coverage · unreproduced hypotheses (separate).<workspace>/receipts/sast-scan-receipt-<ts>.json): base schema + sub_target,
authorization_confirmed, scope, scanner_backend, findings_count, secrets_redacted,
coverage, findings_path, gate_checks. persistence: Spec-Anchored.Done when: authorization + ownership were confirmed (blocking), the owned code was scanned (or the absence recorded NOT-RUN), every reported finding was reproduced, secrets are redacted, each finding has a severity + remediation owner, coverage is stated, and a receipt records the gate checks — the deliverable is a defensive findings report.
Not done if: any scan ran without confirmed authorization/ownership; an unreproduced candidate is reported as a finding; a secret is printed in the clear; a reusable exploit was produced; or an unrun scanner is reported as "clean".
Next step: remediation owners fix the findings; a re-scan confirms closure. product-pentest covers the
running app's attack surface; ai-red-team covers an AI model.
sast-scan is static over source.sast-scan actively scans owned code for
weaknesses; the review reasons about the controls around it.Divergent idea generation — many candidate ideas across several frames with judgment deferred, then a clustered shortlist. Use to open a solution space wide, or /brainstorm. Not for developing one idea (ideate) or picking one (propose).
Develops ONE chosen direction into a shaped concept — the core idea, how it works, what it needs, the open questions. Use to deepen a single idea, or /ideate. Not for generating many (brainstorm) or deciding among them (propose).
Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset).
Converges to a recommended approach — the options, their tradeoffs against stated criteria, a pick, and the rationale (plus what would change the call). Use to decide among approaches, or /propose. Not for generating options (brainstorm) or deep-diving one (ideate).
Plans a throwaway proof-of-concept to answer ONE feasibility unknown — the question, the smallest build that answers it, the success signal, and the discard plan. Use to de-risk before committing, or /prototype. Not for the real build (executor) or deciding (propose).
Produces a REDTEAM-FINDINGS.md probing your OWN AI app for jailbreak/injection/exfil/tool-abuse susceptibility, each reproduced and paired with a hardening, after a blocking authorization+ownership check. Use to red-team an owned AI system defensively.