code-search-exa

code-search-exa is a skill for Claude Code from sasakiblog26-lgtm/exa-mcp-server. It costs 44 tokens per session (437 once invoked), scanned A, original, MIT.

A code-focused web search that finds examples and documentation from sources such as GitHub, Stack Overflow, and technical documentation. It is intended for searches about programming languages, frameworks, libraries, APIs, and errors.

In plain words
What is it for?
Use it to look up API usage, library setup, configuration patterns, framework instructions, and debugging examples, then extract concise, reusable snippets.
Why use it?
It helps when you need a real code example or authoritative syntax instead of a general web search. Language, framework, version, and exact identifier details make results more relevant.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter.

Good fit Use it to look up API usage, library setup, configuration patterns, framework instructions, and debugging examples, then extract concise, reusable snippets.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sasakiblog26-lgtm/exa-mcp-server/code-search
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 sasakiblog26-lgtm/exa-mcp-server --skill code-search
Clone the repo
git clone --depth 1 https://github.com/sasakiblog26-lgtm/exa-mcp-server

Made for: Claude Code.

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 code-search-exa

README.md
[![agentmods](https://agentmods.dev/badge/skills/sasakiblog26-lgtm/exa-mcp-server/code-search/github.svg)](https://agentmods.dev/skills/sasakiblog26-lgtm/exa-mcp-server/code-search)
Your own site
<a href="https://agentmods.dev/skills/sasakiblog26-lgtm/exa-mcp-server/code-search"><img src="https://agentmods.dev/badge/skills/sasakiblog26-lgtm/exa-mcp-server/code-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.

agentmods 80×15 button for code-search-exa

Your own site · 80×15
<a href="https://agentmods.dev/skills/sasakiblog26-lgtm/exa-mcp-server/code-search"><img src="https://agentmods.dev/badge/skills/sasakiblog26-lgtm/exa-mcp-server/code-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 437 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.00044 $0.00437
Opus 5 $0.00022 $0.00218
Sonnet 5 $0.00009 $0.00087
Haiku 4.5 $0.00004 $0.00044

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

Security

Grade A, and why

code-search-exa 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.

skills/code-search/SKILL.md · 61 lines

What it actually says

Code Context (Exa)

Tool Restriction (Critical)

ONLY use web_search_exa. Do NOT use other Exa tools.

Token Isolation (Critical)

Never run Exa in main context. Always spawn Task agents:

  • Agent calls web_search_exa
  • Agent extracts the minimum viable snippet(s) + constraints
  • Agent deduplicates near-identical results (mirrors, forks, repeated StackOverflow answers) before presenting
  • Agent returns copyable snippets + brief explanation
  • Main context stays clean regardless of search volume

When to Use

Use this tool for ANY programming-related request:

  • API usage and syntax
  • SDK/library examples
  • config and setup patterns
  • framework "how to" questions
  • debugging when you need authoritative snippets

Query Writing Patterns (High Signal)

To reduce irrelevant results and cross-language noise:

  • Always include the programming language in the query.
    • Example: use "Go generics" instead of just "generics".
  • When applicable, also include framework + version (e.g., "Next.js 14", "React 19", "Python 3.12").
  • Include exact identifiers (function/class names, config keys, error messages) when you have them.

Return:

  1. Best minimal working snippet(s) (keep it copy/paste friendly)
  2. Notes on version / constraints / gotchas
  3. Sources (URLs if present in returned context)

Before presenting:

  • Deduplicate similar results and keep only the best representative snippet per approach.

MCP Configuration

{
  "servers": {
    "exa": {
      "type": "http",
      "url": "https://mcp.exa.ai/mcp?tools=web_search_exa"
    }
  }
}
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. 9d ago First seen · 61 lines · 44 tokens per session scan A 29084fc73c7a

Subscribe to this mod's changes

code-search-exa is a skill published in the GitHub repository sasakiblog26-lgtm/exa-mcp-server (1 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 437 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