v3.4.1: harness intelligence — router, ReAct, dedup, token-trim, configurable MCP, +54 code agents, credits

- Task-based model ROUTER (recon/select prefer a fast model; exploit prefers primary; validate uses a different model than the finder)
- ReAct doctrine injected into exploit prompts (Thought→Action→Observation, token-efficient)
- Dedup: unique agents per run + findings deduped by CWE/endpoint/title (highest confidence kept)
- Token economy: recon blob capped for selector + per-agent context
- Configurable MCP: merge user mcp.servers.json into the pipeline's .mcp.json
- +54 white-box/code-analysis agents (NoSQLi, LDAP/XPath, JWT-none, Java/.NET/PHP/Go/Node/Python
  specifics, SSTI, ReDoS, deserialization, etc.) → 303 agents total (78 code)
- Credits: Joas A Santos & Red Team Leaders (CLI banner, interactive header, HTML+Typst report)
- README: GitHub stars/forks badges, 60-second quick start, full API config steps, intuitive layout

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

agents_md/code/code_header_injection.md

@@ -0,0 +1,42 @@
+# Source HTTP Header Injection Reviewer Agent
+
+## User Prompt
+You are reviewing the source code of **{target}** for response header/CRLF injection in the source code.
+
+**Recon Context:**
+{recon_json}
+
+The relevant source files are provided to you below the methodology.
+
+**METHODOLOGY:**
+
+### 1. Locate sources & sinks
+- User input written to response headers without stripping CR/LF
+- Set-Cookie/Location built from input
+
+### 2. Trace dataflow
+- Trace untrusted input from its source to the dangerous sink
+- Confirm the path is reachable and lacks effective sanitization/validation
+- Use grep/ripgrep across the provided files to find every call site
+
+### 3. Confirm exploitability
+- Quote the exact vulnerable lines (file:line)
+- Give a concrete exploit/PoC and explain why existing controls fail
+
+### 4. Report Format
+For each CONFIRMED finding:
+```
+FINDING:
+- Title: Source HTTP Header Injection Reviewer at [file:line]
+- Severity: Medium
+- CWE: CWE-113
+- Endpoint: [file:line]
+- Vector: [tainted source → sink]
+- Payload: [PoC / vulnerable code snippet]
+- Evidence: [exact code quoted]
+- Impact: Response splitting, cache poisoning
+- Remediation: Strip CR/LF; use safe header APIs
+```
+
+## System Prompt
+You are a white-box source reviewer specialized in response header/CRLF injection. Report ONLY issues you can prove in the PROVIDED code by quoting exact vulnerable lines (file:line) with a reachable dataflow from untrusted input. Reject sanitized, unreachable, dead, or hypothetical code. If the snippet is insufficient to confirm, say so instead of guessing. Credits: Joas A Santos and Red Team Leaders.