ingest

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Ingest Reconnaissance Files

You are ingesting reconnaissance files to extract vulnerability findings and build engagement context. The target path is: $ARGUMENTS

---

Step 1: Validate Path

If $ARGUMENTS is empty or blank, print this and stop:

Usage: /ingest <path-to-file-or-directory>

Examples:
  /ingest /path/to/recon-notes
  /ingest ./ATTACK-VECTORS.md
  /ingest ./reports/

Use Bash to validate the path exists and resolve it to an absolute path:

realpath "$ARGUMENTS"

Determine if the path is a file or directory using test -f / test -d.

---

Step 2: Discover Files

If single file: Skip to Step 4 (process directly).

If directory: Use Glob to find all ingestible files:

• **/*.md — markdown files
• **/*.json — JSON files (but NOT findings-db.jsonl)
• **/*.txt — text files

Exclude these from results:

• findings-db.jsonl
• engagement-context.md
• Any file starting with .

Count the files. If zero, print "No ingestible files found" and stop.

---

Step 3: Decide Processing Mode

• ≤3 files: Process directly — Read each file yourself and extract findings + context inline (go to Step 4)
• 4+ files: Batch into groups of 5 files and spawn parallel Task subagents (go to Step 5)

---

Step 4: Direct Processing (Single File or ≤3 Files)

Read each file with the Read tool.

For each file, extract:

A. Vulnerability Findings

Identify every distinct vulnerability or security issue mentioned. For each one, extract:

• endpoint: The URL path or endpoint (e.g., /api/auth/reset-password, POST /api/payments/generate)
• vuln_type: Category — idor, sqli, xss, auth-bypass, rce, info-leak, config, rate-limit, user-enum, ssrf, lfi, ssti, xxe, type-confusion, or other
• param: The vulnerable parameter name, or none if not parameter-specific
• severity: CRITICAL, HIGH, MEDIUM, LOW, or INFO
• title: Brief descriptive title (max 80 chars)