get-code-context-exa

A code-search guide that uses Exa to find real examples from GitHub, Stack Overflow, and technical documentation. It is intended for programming questions about APIs, libraries, configuration, and debugging.

In plain words
What is it for?
Finding copyable code snippets and explanations for a specified programming language, framework, library, or API.
Why use it?
It reduces the time spent searching scattered documentation and helps avoid receiving repeated or nearly identical examples.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/tomopay/exa-mcp-server/code-search
Any agent
npx skills add tomopay/exa-mcp-server --skill code-search
Clone the repo
git clone --depth 1 https://github.com/tomopay/exa-mcp-server

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00045 $0.00545
Opus 5 $0.00023 $0.00272
Sonnet 5 $0.00009 $0.00109
Haiku 4.5 $0.00005 $0.00055

Measured 2d ago against content hash cf589b5b4dad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

get-code-context-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 2d 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 · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Context (Exa)

Tool Restriction (Critical)

ONLY use get_code_context_exa. Do NOT use other Exa tools.

Token Isolation (Critical)

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

  • Agent calls get_code_context_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

Inputs (Supported)

get_code_context_exa supports:

  • query (string, required)
  • tokensNum (number, optional; default ~5000; typical range 1000–50000)

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.

Dynamic Tuning

Token strategy:

  • Focused snippet needed → tokensNum 1000–3000
  • Most tasks → tokensNum 5000
  • Complex integration → tokensNum 10000–20000
  • Only go larger when necessary (avoid dumping large context)

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=get_code_context_exa"
    }
  }
}

Read the full file on GitHub · 75 lines

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. 2d ago First seen · 75 lines · 45 tokens per session scan A cf589b5b4dad

Subscribe to this mod's changes

get-code-context-exa is a skill published in the GitHub repository tomopay/exa-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 545 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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens