Skip to content
Security
Command

/cti-recall

Have I seen this before? Check a seed against every prior case BEFORE collecting. Always run this first. Usage: /cti-recall <domain|indicator>

From plugin
cti-expert
4448 skills8 commands
Install
$ npx -y skills add 7onez/cti-expert --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/cti-recall

Context preview

What this command does when you run it.

Have I seen this before? Check a seed against every prior case BEFORE collecting. Always run this first. Usage: /cti-recall <domain|indicator>

Command definition

cti-recall.md
name: cti-recall
description: "Have I seen this before? Check a seed against every prior case BEFORE collecting. Always run this first. Usage: /cti-recall <domain|indicator>"
argument-hint: "<domain|indicator>"

/cti-recall — prior-knowledge check

Load the `cti-expert` skill, then check: `$ARGUMENTS`

**This is the cheapest command in the toolkit and it must run before any collection.** A seed already in the store carries prior case context and possibly an operator attribution.

| Layer | Call | |---|---| | **T1 MCP** | `mcp__intel__domain_verdict` · `mcp__intel__which_cases` | | **T2 CLI** | `python3 scripts/backend/intel.py recall <seed>` |

Accepts a domain or a raw indicator (`favicon:<h>`, `ga:<id>`, `wallet:<coin>:<addr>`, `email:<addr>`, `social:<net>:<handle>`).

Report: which case(s) it appears in, any operator attribution, and known KB facts/edges. An indicator seen across MULTIPLE cases is a cross-case link — surface it prominently.

If the seed is already resolved, **say so and stop**. Do not re-investigate unless asked.

Ships withcti-expert

CTI Expert — Cyber Threat Intelligence & OSINT analysis skill for Claude Code. 67+ commands, 35 techniques, no API keys required.

Get the whole plugin