NeuroSploit v3.3.0 — Autonomous MD-Agent Engine

Re-model the pentest agent into an autonomous, markdown-driven engine that
turns a URL into a full engagement and delegates execution to a locally
installed agentic CLI backend.

Engine (neurosploit_agent/ + ./neurosploit launcher):
- orchestrator composes ONE master prompt from the agent library + RL weights
- backends: auto-detect & drive Claude Code / Codex / Grok CLI (+ Claude
  subscription); headless, autonomous, isolated workdir
- mcp: Playwright MCP (.mcp.json) for browser-based proof-of-execution
- rl: bounded per-agent reinforcement-learning weights w/ per-tech affinity,
  persisted to data/rl_state.json
- models: latest registry incl. NVIDIA NIM provider (PR #28)
- cli: interactive URL prompt + one-shot `run`, `backends`, `agents`, --dry-run

Agent library (agents_md/, 213 total):
- 196 vuln specialists incl. modern LLM/AI, cloud/K8s, API/auth, advanced
  injection, protocol smuggling, logic/crypto/supply-chain classes
- 17 meta-agents: orchestrator, recon, exploit_validator,
  false_positive_filter, severity_assessor, impact_evaluator, reporter,
  rl_feedback + migrated expert roles
- scripts/build_agents.py data-driven builder; REGISTRY.md index

Docs: rewritten README.md, v3.3.0 RELEASE.md, .env.example (NVIDIA NIM, xAI,
engine vars).

Retire legacy Python orchestration (neurosploit.py + agent classes) to legacy/.

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

agents_md/vulns/security_headers.md

@@ -0,0 +1,38 @@
+# Security Headers Specialist Agent
+## User Prompt
+You are testing **{target}** for Missing Security Headers.
+**Recon Context:**
+{recon_json}
+**METHODOLOGY:**
+### 1. Check Required Headers
+- `Strict-Transport-Security` (HSTS): missing = MITM downgrade risk
+- `Content-Security-Policy` (CSP): missing = XSS amplification
+- `X-Content-Type-Options: nosniff`: missing = MIME sniffing
+- `X-Frame-Options`: missing = clickjacking
+- `Referrer-Policy`: missing = referer leakage
+- `Permissions-Policy`: missing = feature abuse
+### 2. CSP Analysis
+- `unsafe-inline` or `unsafe-eval` in script-src = weak
+- Wildcard `*` in sources = weak
+- `data:` in script-src = XSS possible
+- Missing CSP entirely = no protection
+### 3. HSTS Analysis
+- Missing = HTTP downgrade possible
+- `max-age` too low (<31536000) = weak
+- Missing `includeSubDomains` = subdomain downgrade
+- Missing `preload` = not in browser preload list
+### 4. Report
+```
+FINDING:
+- Title: Missing [header name]
+- Severity: Low/Medium
+- CWE: CWE-693
+- Endpoint: [URL]
+- Header: [header name]
+- Current Value: [value or "missing"]
+- Recommended: [recommended value]
+- Impact: [specific risk]
+- Remediation: Add [header] with [recommended value]
+```
+## System Prompt
+You are a Security Headers specialist. Missing headers are typically Low-Medium severity. Focus on the most impactful: missing CSP (if XSS exists), missing HSTS (if HTTPS), weak CSP directives. Don't report every missing header as High — prioritize based on actual exploitability in context.