exa-deep-research

exa-deep-research is a skill for Claude Code, Codex from orchidautomation/pluxx. It costs 46 tokens per session (381 once invoked), scanned A, original, MIT.

A multi-step Exa research workflow for questions that need several searches, source checks, and a final synthesis. It can cover people, companies, code, news, literature reviews, lead generation, and competitive analysis.

In plain words
What is it for?
Use it for deep company or competitor research, literature reviews, news investigations, lead generation, code research, and other source-backed studies.
Why use it?
It is intended for research where one search is not enough, helping gather, inspect, rank, and combine information from multiple sources.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also agents/openai.yaml present. Also seen: agent in frontmatter.

Good fit Use it for deep company or competitor research, literature reviews, news investigations, lead generation, code research, and other source-backed studies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orchidautomation/pluxx/exa-deep-research
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add orchidautomation/pluxx --skill exa-deep-research
Clone the repo
git clone --depth 1 https://github.com/orchidautomation/pluxx

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for exa-deep-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchidautomation/pluxx/exa-deep-research/github.svg)](https://agentmods.dev/skills/orchidautomation/pluxx/exa-deep-research)
Your own site
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/exa-deep-research"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/exa-deep-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for exa-deep-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/exa-deep-research"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/exa-deep-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 381 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00381
Opus 5 $0.00023 $0.00191
Sonnet 5 $0.00009 $0.00076
Haiku 4.5 $0.00005 $0.00038

Measured 10d ago against content hash 47c2839e3344, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

exa-deep-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

example/exa-plugin/skills/exa-deep-research/SKILL.md · 41 lines

What it actually says

Exa Deep Research

Use this skill when the task needs more than one search pass.

What To Load

Workflow

  1. Decide whether the request is simple, moderate, advanced, or complex.
  2. If the task is ambiguous between a quick lookup and a full deep dive, ask the user which depth they want.
  3. Use the strongest matching specialist agents:
    • people-scout
    • company-scout
    • code-scout
    • news-scout
    • source-auditor
    • synthesis-reviewer
  4. Keep raw Exa results out of the main answer whenever delegated agents can compress them first.
  5. Use web_search_advanced_exa when the query needs richer filters, highlights, or tighter control than web_search_exa.
  6. Use web_fetch_exa on the most promising URLs before final synthesis when snippets are not enough.
  7. If the answer would exceed one screen, write the full result set to exa-results/<topic>-<YYYY-MM-DD>.md and keep the in-chat answer compact.

Output

Return:

  • a compact answer that directly solves the user's request
  • citations with URLs
  • the main process or ranking note if it materially affects the answer
Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 41 lines · 46 tokens per session scan A 47c2839e3344

Subscribe to this mod's changes

exa-deep-research is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 381 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens