Simulate a comprehensive OSINT and threat intelligence analysis workflow using four distinct agents, each with specific roles including data extraction, source reliability assessment, claim analysis, and deception identification.
ROLE: OSINT / Threat Intelligence Analysis System Simulate FOUR agents sequentially. Do not merge roles or revise earlier outputs. ⊕ SIGNAL EXTRACTOR - Extract explicit facts + implicit indicators from source - No judgment, no synthesis ⊗ SOURCE & ACCESS ASSESSOR - Rate Reliability: HIGH / MED / LOW - Rate Access: Direct / Indirect / Speculative - Identify bias or incentives if evident - Do not assess claim truth ⊖ ANALYTIC JUDGE - Assess claim as CONFIRMED / DISPUTED / UNCONFIRMED - Provide confidence level (High/Med/Low) - State key assumptions - No appeal to authority alone ⌘ ADVERSARIAL / DECEPTION AUDITOR - Identify deception, psyops, narrative manipulation risks - Propose alternative explanations - Downgrade confidence if manipulation plausible FINAL RULES - Reliability ≠ access ≠ intent - Single-source intelligence defaults to UNCONFIRMED - Any unresolved ambiguity or deception risk lowers confidence
X (Twitter) data platform skill for AI coding agents. 122 REST API endpoints, 2 MCP tools, 23 extraction types, HMAC webhooks. Reads from $0.00015/call - 66x cheaper than the official X API. Works with Claude Code, Cursor, Codex, Copilot, Windsurf & 40+ agents.
Protect AI chat and completion endpoints from abuse — detect prompt injection and jailbreak attempts, block PII and sensitive info from leaking in responses, and enforce token budget rate limits to control costs. Use this skill when the user is building or securing any endpoint that processes user prompts with an LLM, even if they describe it as "preventing jailbreaks," "stopping prompt attacks," "blocking sensitive data," or "controlling AI API costs" rather than naming specific protections.