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 agentmods add skills/mrobinson2/azureagentforge/exa-searchnpx skills add mrobinson2/AzureAgentForge --skill exa-searchgit clone --depth 1 https://github.com/mrobinson2/AzureAgentForgeWrote 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/mrobinson2/azureagentforge/exa-search)<a href="https://agentmods.dev/skills/mrobinson2/azureagentforge/exa-search"><img src="https://agentmods.dev/badge/skills/mrobinson2/azureagentforge/exa-search.svg" alt="Measured on agentmods" 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.00123 | $0.00648 |
| Opus 5 | $0.00062 | $0.00324 |
| Sonnet 5 | $0.00025 | $0.00130 |
| Haiku 4.5 | $0.00012 | $0.00065 |
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 6d 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.
What it actually says
Semantic web search with exa-search
exa-search is a CLI on $PATH that queries the Exa neural
search API and returns results in the same ddgs-compatible JSON shape as
brave-search — an array of {title, href, body} — so it's a drop-in alongside
the other search tools.
When to use which search backend
| Backend | Best for |
|---|---|
exa-search |
Conceptual / semantic / exploratory queries: "frameworks like LangGraph", "research on agent memory", "find articles arguing X". Neural search finds relevant pages even when they don't contain your exact words. |
brave-search |
Fresh / breaking / exact-term queries: news, a specific product page, a known title, anything time-sensitive. |
When a question has both an exploratory and a freshness angle, run both and merge — they surface different pages.
Usage
# Naive form:
exa-search "open-source agent frameworks with durable execution"
# ddgs-compatible form (same flags as brave-search), e.g. 8 results:
exa-search text -k "open-source agent frameworks" -m 8 -o json
Output is a JSON array; each element has title, href, and body (a short
text excerpt from the page). Parse it the same way you parse brave-search
output.
Behavior and exit codes
| Exit | Meaning |
|---|---|
0 |
Success — JSON array on stdout (may be [] if Exa found nothing). |
1 |
EXA_API_KEY is not set. The wrapper can't run without it. |
2 |
Empty query. |
3 / 4 |
Exa API error (non-2xx) or a transport failure — a clear message is printed to stderr. |
Environment
| Variable | Purpose |
|---|---|
EXA_API_KEY |
Required. Exa API key (free tier ~1,000 searches/month). In Azure deploys it is mounted from the exa-api-key Key Vault secret when exa_search_enabled = true. |
If exa-search exits 1, Exa isn't configured in this environment — fall back to
brave-search.
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.
- 6d ago First seen · 60 lines · 123 tokens per session scan A db43482cf49c
exa-search is a skill published in the GitHub repository mrobinson2/AzureAgentForge (21 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 648 once invoked, about $0.0006 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
tomllm-format
.tomllm / .tomllmd = valid TOML + enriched # comment conventions for LLM context.
release
Cut a versioned release and publish everos to PyPI via the tag-triggered workflow.
agentfield-use
Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …
datadesigner-docs
Maintain the NeMo Data Designer Fern docs site under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", "regenerate notebooks", "update dev note", any request that touches fern/.
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…