القائمة
Produces a PENTEST-PLAN.md then PENTEST-FINDINGS.md for your OWN app's attack surface (each finding reproduced, non-destructive, with remediation) after a blocking authorization+ownership check. Use to test an owned app's attack surface defensively.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | product-pentest |
| description | Produces a PENTEST-PLAN.md then PENTEST-FINDINGS.md for your OWN app's attack surface (each finding reproduced, non-destructive, with remediation) after a blocking authorization+ownership check. Use to test an owned app's attack surface defensively. |
The attack-surface producer of the security-testing pack (D5, opt-in). It tests your own authorized
application — injection, auth/session, access control, secrets, misconfiguration — writes a
PENTEST-PLAN.md (scope, method, expected evidence), and on an authorized run records PENTEST-FINDINGS.md
(each finding reproduced against the app, non-destructive, with a remediation owner). It is defensive:
find-and-fix on an app you own, never intrusion on someone else's. Authorization plus ownership is the
blocking precondition — no owned scope, no test.
A pre-execution plan verifies by Review (sound, scoped, safe, non-destructive); the live findings verify by Audit on the authorized run (real, reproduced, remediable). The verifier never fabricates a "tested / clean" for a test that did not run.
Does: confirm authorization + ownership first (blocking); scope the attack surface + boundary (in/out);
choose a non-destructive test method + the expected evidence; write PENTEST-PLAN.md; on an authorized run,
reproduce each finding against the app and record PENTEST-FINDINGS.md with severity + remediation owner;
write a receipt. Does not: test an app it does not own or is not authorized for, exceed the agreed scope, run
a destructive test, move data off the system, produce a reusable exploit/intrusion kit, or claim a result for
an unrun test.
sast-scan; or probing an AI model — that is
ai-red-team. This sub_target tests the running app's surface.security-review.| Situation | Reference |
|---|---|
| Thin inputs / no scope / weaponization or third-party ask | rules/cold-start.md |
| Per-sub_target must-declares · overlay · vocabulary | ../acceptance/sub-targets.md · ../acceptance/overlay.md · ../vocabulary.md |
| Sibling sub_targets (owned source / AI model) | sast-scan · ai-red-team |
../vocabulary.md, ../acceptance/) + state/intake.json.PENTEST-PLAN.md. Scope + boundary + method + expected evidence + the non-destructive rule.
The plan verifies by Review; the live run is deferred until authorized.PENTEST-FINDINGS.md — reproduced findings + remediation + the coverage vs the planned surface.A gate failure is fixed before lock, not waived — these mirror the authorization/testing/engineering gates.
security-test/ if that dir exists) — persistence: Spec-Anchored. Authorized scope + boundary ·
method + expected evidence · non-destructive rule · findings (reproduced, severity, remediation owner) ·
coverage.<workspace>/receipts/product-pentest-receipt-<ts>.json): base schema + sub_target,
authorization_confirmed, scope, attack_classes, non_destructive, findings_count,
run_status, plan_path, findings_path, gate_checks. persistence: Spec-Anchored.Done when: authorization + ownership were confirmed (blocking), a non-destructive PENTEST-PLAN.md scopes
the surface with method + expected evidence (Review-verified), and — on an authorized run — every reported
finding was reproduced within scope with severity + remediation, secrets redacted, and a receipt records the
gate checks.
Not done if: any test ran without confirmed authorization/ownership; the test exceeded scope or was destructive; an unreproduced candidate is reported as a finding; data was exfiltrated; a reusable exploit was produced; or an unrun test is reported as "clean".
Next step: remediation owners fix the findings; a re-test confirms closure. sast-scan covers owned
source; ai-red-team covers an AI model.
product-pentest tests the running app's surface.product-pentest actively tests the live surface; 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.