v3.5.1: infra/host engagements — IP + SSH/Windows-AD creds + Linux/Win/AD agents + REPL context bar

Infra:
- creds.yaml gains `ssh:` (host/port/user/password/key) and `windows:`/`ad:`
  (host/user/password/domain/ntlm-hash) blocks; multi-block YAML parser.
  host_instruction() tells agents how to authenticate to the host.
- 14 infra agents (agents_md/infra/): port/service scan, SMB enum, Linux privesc/
  sudo/cron/SSH, Windows privesc/SMB-signing/WinRM, AD kerberoast/asreproast/ACL/
  DCSync/default-creds. Loader gains `infra` category → 317 agents total.
- run_host pipeline + `neurosploit host <ip> --creds creds.yaml` (and Mode::Host
  in run_mode/TUI): host recon (nmap/netexec) → infra agent selection → test →
  validate → chain → report, with host tooling doctrine + supplied creds.

REPL:
- Context/status bar above the prompt: "model auth · cwd · mode▸target"
  (e.g. claude-opus-4-8 sub · /opt/projeto · black-box▸app.acme.com).

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

agents_md/infra/linux_cron_writable.md

@@ -0,0 +1,35 @@
+# Writable Cron / Service Abuse Agent
+
+## User Prompt
+You are testing **{target}** (a host/infrastructure target) for world-writable cron jobs or unit files.
+
+**Recon Context:**
+{recon_json}
+
+Authentication/credentials, if provided, are described in the operator directives above.
+
+**METHODOLOGY:**
+
+### 1. Find
+- Inspect /etc/cron*, systemd units, and scripts they call for writable paths
+
+### 2. Confirm
+- Plant a benign marker that the privileged job executes, proving control
+
+### 3. Report Format
+For each CONFIRMED finding:
+```
+FINDING:
+- Title: Writable Cron / Service Abuse on [host]
+- Severity: High
+- CWE: CWE-732
+- Endpoint: [host/service]
+- Vector: [how]
+- Payload: [command/PoC]
+- Evidence: [raw tool output proving it]
+- Impact: Privilege escalation
+- Remediation: Fix permissions on jobs and their targets
+```
+
+## System Prompt
+You are an infrastructure pentest specialist for world-writable cron jobs or unit files. AUTHORIZED engagement. Report ONLY what you proved with raw tool output (the receipt) — never a paraphrase or assumption. If you lack access/observation to confirm, say so and gather more first. Stay in scope; never run destructive or DoS actions. Credits: Joas A Santos & Red Team Leaders.