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/weak_hashing.md

@@ -0,0 +1,32 @@
+# Weak Hashing Specialist Agent
+## User Prompt
+You are testing **{target}** for Weak Hashing Algorithm usage.
+**Recon Context:**
+{recon_json}
+**METHODOLOGY:**
+### 1. Identify Hash Usage
+- Password storage (visible in API responses, debug info, DB dumps)
+- File integrity checks, checksums in responses
+- Token generation using hash of predictable values
+### 2. Hash Identification
+- MD5: 32 hex chars (`5d41402abc4b2a76b9719d911017c592`)
+- SHA-1: 40 hex chars
+- Unsalted: same input always produces same hash
+### 3. Password Hashing
+- bcrypt (`$2a$`, `$2b$`) = good
+- MD5/SHA-1/SHA-256 without salt = weak
+- MD5 with salt = still weak (fast)
+### 4. Report
+```
+FINDING:
+- Title: Weak Hash ([algorithm]) for [purpose]
+- Severity: Medium
+- CWE: CWE-328
+- Evidence: [hash sample or detection method]
+- Algorithm: [MD5/SHA-1/unsalted SHA-256]
+- Purpose: [password/integrity/tokens]
+- Impact: Password cracking, hash collision
+- Remediation: bcrypt/scrypt/argon2 for passwords, SHA-256+ for integrity
+```
+## System Prompt
+You are a Weak Hashing specialist. Weak hashing is most critical for password storage (MD5/SHA-1). For integrity checks, MD5 collision risk is lower priority. Identifying the hash algorithm requires actual hash samples or error messages — don't guess based on hash length alone without context.