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 tomopay/exa-mcp-server --skill personal-site-searchgit clone --depth 1 https://github.com/tomopay/exa-mcp-serverWrote 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/tomopay/exa-mcp-server/personal-site-search)<a href="https://agentmods.dev/skills/tomopay/exa-mcp-server/personal-site-search"><img src="https://agentmods.dev/badge/skills/tomopay/exa-mcp-server/personal-site-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/tomopay/exa-mcp-server/personal-site-search"><img src="https://agentmods.dev/badge/skills/tomopay/exa-mcp-server/personal-site-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.00047 | $0.00726 |
| Opus 5 | $0.00023 | $0.00363 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
web-search-advanced-personal-site 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 10d 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 web-search-advanced-personal-site — 0 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Search Advanced - Personal Site Category
Tool Restriction (Critical)
ONLY use web_search_advanced_exa with category: "personal site". Do NOT use other categories or tools.
Full Filter Support
The personal site category supports ALL available parameters:
Core
query(required)numResultstype("auto", "fast", "deep", "neural")
Domain filtering
includeDomainsexcludeDomains(e.g., exclude Medium if you want independent blogs)
Date filtering (ISO 8601)
startPublishedDate/endPublishedDatestartCrawlDate/endCrawlDate
Text filtering
includeText(must contain ALL)excludeText(exclude if ANY match)
Array size restriction: includeText and excludeText only support single-item arrays. Multi-item arrays (2+ items) cause 400 errors. To match multiple terms, put them in the query string or run separate searches.
Content extraction
textMaxCharacters/contextMaxCharactersenableSummary/summaryQueryenableHighlights/highlightsNumSentences/highlightsPerUrl/highlightsQuery
Additional
additionalQueriesmaxAgeHours/livecrawlTimeoutsubpages/subpageTarget- useful for exploring portfolio sites
Token Isolation (Critical)
Never run Exa searches in main context. Always spawn Task agents:
- Agent calls
web_search_advanced_exawithcategory: "personal site" - Agent merges + deduplicates results before presenting
- Agent returns distilled output (brief markdown or compact JSON)
- Main context stays clean regardless of search volume
When to Use
Use this category when you need:
- Individual expert opinions and experiences
- Personal blog posts on technical topics
- Portfolio websites
- Independent analysis (not corporate content)
- Deep dives and tutorials from practitioners
Examples
Technical blog posts:
web_search_advanced_exa {
"query": "building production LLM applications lessons learned",
"category": "personal site",
"numResults": 15,
"type": "deep",
"enableSummary": true
}
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.
- 10d ago First seen · 104 lines · 47 tokens per session scan A 4c957bb32665
web-search-advanced-personal-site is a skill published in the GitHub repository tomopay/exa-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 726 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 web-search-advanced-personal-site, differing in 0 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…