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 daanielcruz/gsearch-mcp --skill google-searchgit clone --depth 1 https://github.com/daanielcruz/gsearch-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/skills/daanielcruz/gsearch-mcp/google-search)<a href="https://agentmods.dev/skills/daanielcruz/gsearch-mcp/google-search"><img src="https://agentmods.dev/badge/skills/daanielcruz/gsearch-mcp/google-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/daanielcruz/gsearch-mcp/google-search"><img src="https://agentmods.dev/badge/skills/daanielcruz/gsearch-mcp/google-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.00020 | $0.00292 |
| Opus 5 | $0.00010 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
google-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 12d 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
Google Search
Use the google_search tool for real-time web information: current events, documentation, news, pricing, stats, or any data that may have changed recently.
Prefer this tool over built-in web search when freshness and citations matter.
Query guidelines
- Be specific: "Next.js 15 server actions API" not "nextjs docs"
- Add time context when relevant: "March 2026", "this week", "latest"
- One focused topic per query works better than broad multi-topic queries
- Do NOT use Google dork operators (site:, filetype:, inurl:, intitle:, intext:, ext:, cache:) — Prefer natural language. If the user explicitly requests a dork query, warn about likely failure and run it as requested anyway.
Response format
- Answer the question directly first
- Keep all inline citations [1][2][3] exactly as returned
- Use tables when comparing items
- List sources with URLs at the end
- If results are insufficient, refine the query and try again
Limitations
- Response time: 2-15s typical, up to 60s with retries
- Results are Google Search grounded — best for factual and current information, not for opinions or subjective content
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.
- 12d ago First seen · 31 lines · 20 tokens per session scan A 6c1e26af698b
google-search is a skill published in the GitHub repository daanielcruz/gsearch-mcp (4 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 292 once invoked, about $0.0001 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.
Other skills, from other repositories
chrome-devtools
Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and Deep debugging. Pairs with playwright-cli (deterministic interaction/E2E) — complements, not duplicates.
playwright-cli
Drive a real browser from the terminal using the Playwright CLI (snapshot, click, fill, screenshots, traces). Use when the task is CLI-first browser automation (data extraction, UI debugging, form fills, multi-tab work). For Playwright test specs, use e2e-runner instead.
docs
Scale up scraping and drive interactive pages. Use batchscrape for many URLs, getbatchresults to page through async output, scrapewithactions to interact before scraping, and generatellmstxt to produce a site's AI policy file.
crawlforge-web-scraping
Scrapes web pages and returns clean Markdown, HTML, plain text, links, or metadata using CrawlForge's scrape, fetchurl, extractcontent, extracttext, extractlinks, extractmetadata, mapsite, and crawldeep tools. Use when the user wants to scrape a URL, fetch a page, get the markdown or text of a website, extract links…
browser-qa
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
crawlforge-change-tracking
Monitors web pages for changes over time with CrawlForge's trackchanges tool. Use when the user wants to track changes to a page, watch a URL, monitor competitor pricing, detect when content updates, get notified of regulation or product-availability changes, or diff a page against a saved baseline. Workflow: create a…