/findings

description: Search and view the findings database
allowed-tools: Bash, Read, Grep
argument-hint: [search-term] [--severity critical|high|medium|low|info] [--type sqli|xss|idor|rce|auth|config|info-leak]

You are querying the Elliot findings database (`findings-db.jsonl`). Use the findings-tracker.js script to retrieve and display results.

The tracker script is located at: `${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js`

Argument Handling

Parse the user's arguments from `$ARGUMENTS`:

1. **No arguments**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list` first to show the table, then `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summary` for the stats.

2. **`--severity <level>`**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --severity <level>`

3. **`--type <vuln_type>`**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --type <vuln_type>`

4. **Any other text** (search term): Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" search <term>`

5. **`summary`**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summary`

6. **`--html`** (anywhere in arguments): Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" html` with any additional filters (`--severity`, `--type`, `--status`) passed through. The script writes an HTML file and prints the path. Show the path to the user.

Output Format

Present the results in a clean, readable format. If the tracker outputs a table, pass it through directly. For summary output, present the counts prominently.

If no findings exist yet, mention that findings are auto-recorded when Hexstrike scans detect vulnerabilities, and suggest running a scan command like `/webscan` or `/apiscan`.