Agent skill · security · jeremylongshore
exa-security-basics
Threat-model Exa credentials, query intent, retrieved web content, generated output, and retained operational evidence as separate trust boundaries. Use when operating or reviewing this Exa boundary. Trigger with "Exa security basics", "review Exa security basics", or "fix Exa security basics".
Why this skill is useful
Provides specific API key management practices and content moderation patterns for Exa that the AI wouldn't reliably generate on its own.
What it needs
Requires exa account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Security and Data Boundary Overview Threat-model Exa credentials, query intent, retrieved web content, generated output, and retained operational evidence as separate trust boundaries. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Exa is SOC 2 Type II certified and offers enterprise controls such as Zero Data Retention and HIPAA enablement. HIPAA mode is request-scoped, supports only eligible Search and Contents cache-only retrieval, and rejects summaries or live freshness. Regional access restrictions can yield Cloudflare block pages rather than Exa JSON. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Classify queries, URLs, retrieved content, outputs, identifiers, and credentials separately. 2. Confirm team plan and enterprise controls before asserting compliance. 3. Keep API and service keys server-side with narrow ownership and rotation. 4. Apply moderation, domain policy, output validation, and prompt-injection defenses. 5. Store only approved evidence and propagate deletion or retention decisions downstream. 6. Test credential revocation, policy denial, regional blocks, and incident escalation. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-security-basics--740857