From OSINT GEOINT
Hunts GPS jamming and spoofing events globally, estimates emitter location with confidence and CEP, and identifies affected aircraft.
How this command is triggered — by the user, by Claude, or both
Slash command
/osint-geoint:osint-jamming place | lat lon | globalThe summary Claude sees in its command listing — used to decide when to auto-load this command
Hunt GPS jamming for: **$ARGUMENTS** Follow the jammer-hunt playbook: 1. `get_situation()` → read `gps_jamming.high` (any high-severity cells worldwide?). 2. `gps_jamming(area or global)` → the worst cell's centre. 3. `focus_area(lat, lon, 300)` → a fresh, un-rate-limited pull of that region. 4. `locate_emitter(lat, lon, 300)` → weighted-centroid estimate + CEP + confidence. State clearly it is a **footprint estimate (~tens of km), not RF direction-finding**. 5. `query_aircraft(lat, lon, gnss_degraded=True, detail='long')` → the affected aircraft, to corroborate the footprint with real tr...
Hunt GPS jamming for: $ARGUMENTS
Follow the jammer-hunt playbook:
get_situation() → read gps_jamming.high (any high-severity cells worldwide?).gps_jamming(area or global) → the worst cell's centre.focus_area(lat, lon, 300) → a fresh, un-rate-limited pull of that region.locate_emitter(lat, lon, 300) → weighted-centroid estimate + CEP + confidence. State clearly it is a footprint estimate (~tens of km), not RF direction-finding.query_aircraft(lat, lon, gnss_degraded=True, detail='long') → the affected aircraft, to corroborate the footprint with real tracks.detect_deception(lat, lon) → rule out that this is GPS spoofing (position injection) rather than jamming.Report: emitter estimate ±CEP, affected-aircraft count, confidence, and caveats.
npx claudepluginhub andrewctf/velocity --plugin osint-geoint/incident-reportingGuides through DORA major ICT incident classification and reporting, producing structured reports for regulatory submission.
/breach-processGuides GDPR breach notification compliance, covering detection, assessment, notification, and documentation phases with 72-hour rule requirements.
/data-residencyVerifies data residency posture for ITAR (US-located by default) and EAR (BIS-driven sanctions). Accepts optional framework and cloud provider arguments.
/search-threatsSearches Abnormal Security for email threats using filters like sender, recipient, attack type, keywords, and date range. Returns a table of threats with severity, subject, status, and AI insights.
/hunt-threatHunts for a specific threat across managed environments using natural language description, generates PowerQuery via Purple AI, and executes it against the SentinelOne Data Lake.
/reconRuns a full recon pipeline on a target — subdomain enumeration, live host discovery, URL crawling, bug class classification, and nuclei scanning. Outputs to recon/<target>/.