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 BenedictKing/benedictking-skills --skill exa-searchgit clone --depth 1 https://github.com/BenedictKing/benedictking-skillsWrote 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/benedictking/benedictking-skills/exa-search)<a href="https://agentmods.dev/skills/benedictking/benedictking-skills/exa-search"><img src="https://agentmods.dev/badge/skills/benedictking/benedictking-skills/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/benedictking/benedictking-skills/exa-search"><img src="https://agentmods.dev/badge/skills/benedictking/benedictking-skills/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.00036 | $0.01294 |
| Opus 5 | $0.00018 | $0.00647 |
| Sonnet 5 | $0.00007 | $0.00259 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exa Search Skill
Trigger Conditions & Endpoint Selection
Choose Exa endpoint based on user intent:
- search: Need semantic search / find web pages / research topics. Use
type: "auto"by default. - deep search / structured research: Use the search endpoint with
type: "deep"ortype: "deep-reasoning"and optionaloutputSchema. - contents: Given result IDs, need to extract full content.
- findsimilar: Given URL, need to find similar pages.
- answer: Need direct answer to a question.
/research and /research/v1 are deprecated and were hard-removed on 2026-05-01. Do not use them for new calls; migrate research-style requests to /search with type: "deep-reasoning".
Recommended Architecture (Main Skill + Sub-skill)
This skill uses a two-phase architecture:
- Main skill (current context): Understand user question → Choose endpoint → Assemble JSON payload
- Sub-skill (fork context): Only responsible for HTTP call execution, avoiding conversation history token waste
Execution Method
Use Task tool to invoke exa-fetcher sub-skill, passing command and JSON (stdin):
Task parameters:
- subagent_type: Bash
- description: "Call Exa API"
- prompt: cat <<'JSON' | node scripts/exa-api.cjs <search|contents|findsimilar|answer>
{ ...payload... }
JSON
The script still accepts the legacy research command for backwards compatibility, but it normalizes the payload and sends it to /search with type: "deep-reasoning".
Payload Examples
1) Search
cat <<'JSON' | node scripts/exa-api.cjs search
{
"query": "Latest research in LLMs",
"type": "auto",
"numResults": 10,
"category": "research paper",
"includeDomains": [],
"excludeDomains": [],
"startPublishedDate": "2025-01-01",
"endPublishedDate": "2025-12-31",
"contents": {
"highlights": true,
"summary": true
}
}
JSON
Search Types:
auto: Balanced defaultfast: Low latencyinstant: Lowest latencydeep-lite: Lightweight synthesized outputdeep: Multi-step search with reasoning and structured outputsdeep-reasoning: Highest-effort deep search for complex research tasks
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.
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.
- 11d ago First seen · 179 lines · 36 tokens per session scan A ff4b3c2fc946
exa-search is a skill published in the GitHub repository BenedictKing/benedictking-skills (14 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,294 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-30.
Other skills, from other repositories
My Skill
Content here.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
writing-quality
Removes common AI writing patterns while preserving meaning, evidence, structure, and SDDP traceability. Ambient through AGENTS.md; not directly invokable.