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 instructions/gregpriday/ask-google-mcp/claude-mdgit clone --depth 1 https://github.com/gregpriday/ask-google-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/instructions/gregpriday/ask-google-mcp/claude-md)<a href="https://agentmods.dev/instructions/gregpriday/ask-google-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/gregpriday/ask-google-mcp/claude-md.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 | $0.02380 | $0.02380 |
| Opus 5 | $0.01190 | $0.01190 |
| Sonnet 5 | $0.00476 | $0.00476 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
ask-google-mcp CLAUDE.md 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 today.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server that provides AI-powered Google search using Gemini with search grounding. It enables Claude Desktop and other MCP clients to perform real-time web searches with AI-synthesized answers and citations.
Key Technologies:
- MCP SDK (
@modelcontextprotocol/sdk) for stdio server transport and JSON-RPC 2.0 communication - Google Generative AI SDK (
@google/generative-ai) for Gemini API integration - Node.js native test runner for unit/integration testing
- ES modules (
type: "module"in package.json)
Development Commands
Running the Server
npm start # Start MCP server
npm run start:checked # Validate .env first, then start
npm run dev # Auto-reload mode with --watch flag
Testing
npm test # Unit tests only (test/unit/**/*.test.js)
npm run test:integration # Integration test with live Gemini API
npm run test:all # All tests (unit + integration)
Running a single test file:
node --test test/unit/tool-handler.test.js
Environment & Security
npm run check-env # Validate .env configuration
npm run security:audit # Check for vulnerabilities
npm run security:fix # Auto-fix security issues
npm run security:update # Update deps and audit
Architecture
MCP Server Design
The server implements a single-tool MCP server following the stdio transport pattern:
-
Server Initialization (src/index.js:117-128)
- Creates MCP Server instance with name/version metadata
- Declares
toolscapability - Connects to StdioServerTransport for JSON-RPC communication
-
Tool Registration (src/index.js:131-176)
- Handles
ListToolsRequestSchemato expose theask_googletool - Tool description is optimized for AI agent invocation with clear trigger phrases
- Input schema includes validation rules and examples
- Handles
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.
- today Changed da3a72e6a466
- 4d ago First seen · 183 lines · 2,380 tokens per session scan A 62c9b64d3118
ask-google-mcp CLAUDE.md is an instructions file published in the GitHub repository gregpriday/ask-google-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 2,380 tokens to every session, about $0.0119 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-release stance: foundation over blast radius, repository layout, commands and host sandbox failures.