Recommended usage
Because a post-script runs once per finding with the full finding and scan context, it's the right place for follow-up work that only makes sense after a vulnerability has been identified.
Validation
Have the model re-examine a finding and judge whether it's real and reachable, then emit a verdict you can filter on:
Re-check "{{summary}}" ({{vulnerability_type}}) at {{file_path}}:{{line}}.
Is it exploitable in a default deployment?
Return:
- verdict (string): CONFIRMED, LIKELY, or FALSE_POSITIVE
- reasoning (string)
Cut noise by grading each finding's exploitability before a human ever looks at it.
Reports
Generate a full, shareable write-up per finding using the reserved _reserved_report key
(rendered as a Report tab on the finding - see
reserved post-scripts).
Produce a polished Markdown report ready to attach to a bug-bounty submission.
Proofs of concept
Ask the model to produce working exploit steps or code using the reserved _reserved_poc
key (rendered as a PoC tab).
Turn a described vulnerability into a concrete, reproducible proof of concept.
You can attach several post-scripts to one scan; each runs on every finding. Next: the reserved post-scripts.