/cti-case
Run the full deterministic pipeline on one or more seeds: collect, ingest, prior-overlap, risk, cluster, ICD-203 assessment. Usage: /cti-case <CASE-ID> <seed> [seed...]
$ npx -y skills add 7onez/cti-expert --agent claude-codeHow 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-case
Context preview
What this command does when you run it.
Run the full deterministic pipeline on one or more seeds: collect, ingest, prior-overlap, risk, cluster, ICD-203 assessment. Usage: /cti-case <CASE-ID> <seed> [seed...]
Command definition
cti-case.mdname: cti-case description: "Run the full deterministic pipeline on one or more seeds: collect, ingest, prior-overlap, risk, cluster, ICD-203 assessment. Usage: /cti-case <CASE-ID> <seed> [seed...]" argument-hint: "<CASE-ID> <seed> [seed...]"
/cti-case — full pipeline
Load the `cti-expert` skill, then open a case for: `$ARGUMENTS`
First argument is the case ID; the rest are seeds. Write the seeds to a file, then:
python3 scripts/backend/intel.py pipeline open <CASE-ID> <seeds-file>
This runs, in order: **collect → ingest → prior-overlap → risk → shared-cluster → assessment**, persisting to `$INTEL_HOME/cases/<CASE-ID>/` with `raw/`, `shared.txt`, `case_graph.json` and `assessment.md`.
Prefer this over hand-running collectors. It records evidence archiving, a versioned assessment and a convergence check that ad-hoc collection does not.
Afterwards:
1. Read `shared.txt` — the shared-indicator set is where the real cluster lives. 2. Run `/cti-check` on every indicator before treating it as a cluster edge. 3. Keep refuted candidates in `cases/<CASE-ID>/refuted/` — a rejected lead is a finding and it stops the next analyst re-chasing it.
**Hostile target?** Collect passively (Wayback/urlscan) or via a proxy range. Never touch a hostile host from an attributable session.
CTI Expert — Cyber Threat Intelligence & OSINT analysis skill for Claude Code. 67+ commands, 35 techniques, no API keys required.
Repo: 7onez/cti-expert
Other commands on cti-expert.
- /cti-check
False-positive control — is this indicator a real operator link or shared noise? Run BEFORE clustering on anything. Usage: /cti-check <indicator>
Open command - /cti-cluster
Expand and correlate an existing case — peers, shared indicators, TLS overlap, reverse-WHOIS. Usage: /cti-cluster <domain|CASE-ID>
Open command - /cti-pivot
Collect pivot artifacts from ONE target — favicon, trackers, wallets, emails, CORS, mail/SPF/DMARC, WHOIS, co-tenancy. Usage: /cti-pivot <url|domain|ip> [--passive]
Open 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>
Open command - /cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report <CASE-ID> [--graph|--pdf]
Open command - /cti-status
Health check — backend tier, case store, MCP tools, API credit balances. Run this when something behaves oddly. Usage: /cti-status
Open command