/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]
$ 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-pivot
Context preview
What this command does when you run it.
Collect pivot artifacts from ONE target — favicon, trackers, wallets, emails, CORS, mail/SPF/DMARC, WHOIS, co-tenancy. Usage: /cti-pivot <url|domain|ip> [--passive]
Command definition
cti-pivot.mdname: cti-pivot description: "Collect pivot artifacts from ONE target — favicon, trackers, wallets, emails, CORS, mail/SPF/DMARC, WHOIS, co-tenancy. Usage: /cti-pivot <url|domain|ip> [--passive]" argument-hint: "<url|domain|ip> [--passive]"
/cti-pivot — single-target collection
Load the `cti-expert` skill, then collect from: `$ARGUMENTS`
| Layer | Call | |---|---| | **T1 MCP** | `mcp__intel__pivot_extract` (url, case) | | **T2 CLI** | `python3 scripts/backend/intel.py pivot-extract <url> --pretty -o <out>` |
A **bare IP** switches to IPPivot mode: ASN/abuse, co-hosted domains, ports, passive DNS. Note that co-tenancy on a shared/reseller box is information, **not** a same-operator link — check the tenant count before drawing any conclusion.
`--passive` works from already-saved or archived HTML instead of contacting the target. Use it for anything hostile.
**If it returns zero or near-zero pivots**, do not stop — run `mcp__intel__fallback_probe`. Parked apex domains routinely have live subdomains; enumerate CT and the Wayback CDX host histogram before writing the seed off.
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-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...]
Open command - /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-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