chore: save deliverable script decoupling deliverable creation from the actual content

prompts/pipeline-testing/exploit-xss.txt

@@ -19,9 +19,10 @@
    ```
 
 ### Step 2: Create Required Deliverable
-Create file `deliverables/xss_exploitation_evidence.md` with content:
-```
-# XSS Exploitation Evidence (Pipeline Test)
+Use the save_deliverable script to create your evidence:
+
+```bash
+node save_deliverable.js XSS_EVIDENCE '# XSS Exploitation Evidence (Pipeline Test)
 
 **MCP Server Used:** {{MCP_SERVER}}
 **Test Site:** https://example.com
@@ -31,7 +32,7 @@ Create file `deliverables/xss_exploitation_evidence.md` with content:
 ## Exploitation Results
 - **Target:** Test XSS vulnerability
 - **Method:** Reflected XSS via search parameter
-- **Evidence:** Successfully executed payload `<script>alert('XSS')</script>`
+- **Evidence:** Successfully executed payload `<script>alert('"'"'XSS'"'"')</script>`
 - **Impact:** Demonstrated JavaScript code execution in user context
 - **Proof:** Pipeline testing mode - simulated successful exploitation
 
@@ -39,8 +40,10 @@ Create file `deliverables/xss_exploitation_evidence.md` with content:
 - **Vulnerability ID:** XSS-VULN-01
 - **Exploitation Status:** Simulated Success (Pipeline Test)
 - **MCP Instance:** {{MCP_SERVER}}
-- **Attack Vector:** Reflected XSS in search functionality
+- **Attack Vector:** Reflected XSS in search functionality'
 ```
 
+This will automatically create `deliverables/xss_exploitation_evidence.md`.
+
 ### Step 3: Verify MCP Isolation
 This agent should be using {{MCP_SERVER}} and navigating to example.com independently of other parallel exploitation agents.