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.
git clone --depth 1 https://github.com/HasData/google-search-mcpWrote 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/commands/hasdata/google-search-mcp/serp-snapshot)<a href="https://agentmods.dev/commands/hasdata/google-search-mcp/serp-snapshot"><img src="https://agentmods.dev/badge/commands/hasdata/google-search-mcp/serp-snapshot/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/commands/hasdata/google-search-mcp/serp-snapshot"><img src="https://agentmods.dev/badge/commands/hasdata/google-search-mcp/serp-snapshot.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.00018 | $0.00242 |
| Opus 5.5 | $0.00007 | $0.00097 |
| Sonnet 5.5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
serp-snapshot 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 23d 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
Take a keyword and report what Google actually shows for it.
Ask me for the keyword and the market if I have not given them. The market is a country and a language, and it changes the answer, so do not guess it silently.
Then:
- Call
hasdata_google_serp_serp_getSearchResultswith the keyword,location,glandhlset to that market. - List the top ten organic results as position, title and domain. Mark the ones that are our own domain if I named one.
- If the response carries an AI Overview block, expand it with
hasdata_google_serp_ai_overview_getAiOverviewResponseusing thepageTokenfrom that block, and list the sources it cites. - List the People Also Ask questions verbatim.
- Close with what the page is made of: how many organic results, whether ads, shopping, video or a knowledge panel are present.
Report what came back. If there is no AI Overview, say so rather than describing what usually appears.
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.
- 23d ago First seen · 18 lines · 18 tokens per session scan A c8bdd6530b24
serp-snapshot is a command published in the GitHub repository HasData/google-search-mcp (17 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 242 once invoked, about $0.0001 per session on Opus 5.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-09-23.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
init
Initialize configurations for Supabase local development.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.