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.
npx skills add KratosAR/claude-code-arsenal --skill exa-searchgit clone --depth 1 https://github.com/KratosAR/claude-code-arsenalWrote 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.
[](https://agentmods.dev/skills/kratosar/claude-code-arsenal/exa-search)<a href="https://agentmods.dev/skills/kratosar/claude-code-arsenal/exa-search"><img src="https://agentmods.dev/badge/skills/kratosar/claude-code-arsenal/exa-search/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.
<a href="https://agentmods.dev/skills/kratosar/claude-code-arsenal/exa-search"><img src="https://agentmods.dev/badge/skills/kratosar/claude-code-arsenal/exa-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00863 |
| Opus 5 | $0.00024 | $0.00432 |
| Sonnet 5 | $0.00010 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
exa-search 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 9d 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.
This is a copy
100% identical to exa-search — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exa Search
Neural search for web content, code, companies, and people via the Exa MCP server.
When to Activate
- User needs current web information or news
- Searching for code examples, API docs, or technical references
- Researching companies, competitors, or market players
- Finding professional profiles or people in a domain
- Running background research for any development task
- User says "search for", "look up", "find", or "what's the latest on"
MCP Requirement
Exa MCP server must be configured. Add to ~/.claude.json:
"exa-web-search": {
"command": "npx",
"args": ["-y", "exa-mcp-server"],
"env": { "EXA_API_KEY": "YOUR_EXA_API_KEY_HERE" }
}
Get an API key at exa.ai.
This repo's current Exa setup documents the tool surface exposed here: web_search_exa and get_code_context_exa.
If your Exa server exposes additional tools, verify their exact names before depending on them in docs or prompts.
Core Tools
web_search_exa
General web search for current information, news, or facts.
web_search_exa(query: "latest AI developments 2026", numResults: 5)
Parameters:
| Param | Type | Default | Notes |
|---|---|---|---|
query |
string | required | Search query |
numResults |
number | 8 | Number of results |
type |
string | auto |
Search mode |
livecrawl |
string | fallback |
Prefer live crawling when needed |
category |
string | none | Optional focus such as company or research paper |
get_code_context_exa
Find code examples and documentation from GitHub, Stack Overflow, and docs sites.
get_code_context_exa(query: "Python asyncio patterns", tokensNum: 3000)
Parameters:
| Param | Type | Default | Notes |
|---|---|---|---|
query |
string | required | Code or API search query |
tokensNum |
number | 5000 | Content tokens (1000-50000) |
Usage Patterns
Quick Lookup
web_search_exa(query: "Node.js 22 new features", numResults: 3)
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.
- 9d ago First seen · 110 lines · 49 tokens per session scan A 3a93153f74f2
exa-search is a skill published in the GitHub repository KratosAR/claude-code-arsenal (2 stars, last pushed 22d ago), licensed MIT. It adds 49 tokens to every session and 863 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to exa-search, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…