Borrowing it
Nothing to install: this file belongs to A1-x-Tech/mcp-google-contacts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/A1-x-Tech/mcp-google-contacts/main/CLAUDE.mdgit clone --depth 1 https://github.com/A1-x-Tech/mcp-google-contactsWrote 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/a1-x-tech/mcp-google-contacts/claude-md)<a href="https://agentmods.dev/instructions/a1-x-tech/mcp-google-contacts/claude-md"><img src="https://agentmods.dev/badge/instructions/a1-x-tech/mcp-google-contacts/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.1 | $0.02436 | $0.02436 |
| Opus 5 | $0.01218 | $0.01218 |
| Sonnet 5 | $0.00487 | $0.00487 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
mcp-google-contacts 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — mcp-google-contacts
MCP server for the Google People API v1 — the API behind Google Contacts —
(TypeScript, stdio). Mixed read/write: tools cover contact list/search/read,
contact CRUD, contact groups and membership, batch mutations and read-only
"Other contacts"; raw_request is the escape hatch. The server talks to
https://people.googleapis.com with a Bearer token; the token is minted from an
OAuth2 refresh token via https://oauth2.googleapis.com/token (or a static
GOOGLE_CONTACTS_ACCESS_TOKEN, mostly for testing).
Commands
npm run dev # run from source (tsx watch)
npm test # unit tests + dist smoke, no network
npm run typecheck # types for src + tests
npm run build # emit dist/
npm run smoke # live READ-ONLY check (refresh-flow creds; optional resource argv/GOOGLE_CONTACTS_SMOKE_RESOURCE)
npm run smoke -- --live # opt-in live WRITE scenario on disposable resources, cleanup in finally
Architecture
src/config.ts— env → config. Credentials: either the refresh tripleGOOGLE_CONTACTS_CLIENT_ID+GOOGLE_CONTACTS_CLIENT_SECRET+GOOGLE_CONTACTS_REFRESH_TOKEN(all three orConfigErrorincomplete_oauth_config) orGOOGLE_CONTACTS_ACCESS_TOKEN; optionalGOOGLE_CONTACTS_API_BASE,GOOGLE_CONTACTS_TIMEOUT_MS,GOOGLE_CONTACTS_MAX_RETRIES. No credentials at all is NOT an error: the fields stayundefinedand the server starts degraded. Also home toCredentialsError/MISSING_CREDENTIALS_MESSAGE(opens with the historical startup error verbatim, then names the variables and the restart) andhasCredentials().src/client.ts— all HTTP and all wire mapping. Token lifecycle (cache until ~60s before expiry, dedupe concurrent refreshes, one forced re-mint + replay on 401);request()resolves the path against the base and rejects foreign origins (SSRF guard), enforces an AbortController timeout that also covers reading the body, retries 429 always but 5xx/network errors only for GET — replaying a write after an ambiguous failure would apply it twice — and throwsGoogleContactsError(status, body). Array query values become repeated params (resourceNames=a&resourceNames=bforpeople:batchGet).buildPerson()maps the normalized contact vocabulary (given_name/emails/phones/... inContactFields) to the wire Person and returns the touched field groups — that list IS the computedupdatePersonFieldsmask. Etag handling lives here too:updateContact/updateContactGroup/batchUpdateContactsfetch the current etag when the caller has none (one extra read; batch uses a singlebatchGet).searchContacts/searchOtherContactssend the documented warmup request (empty query) once per endpoint per session — never retried, failures swallowed — before the first real query, not before every search.src/tools/contacts.ts—list_contacts,search_contacts,get_contact,batch_get_contacts,create_contact,update_contact,delete_contact.src/tools/groups.ts—list_contact_groups,get_contact_group,create_contact_group,update_contact_group,delete_contact_group,modify_group_members.src/tools/batch.ts—batch_create_contacts,batch_update_contacts,batch_delete_contacts.src/tools/other.ts—list_other_contacts(list or, withquery, search),copy_other_contact.src/tools/raw.ts—raw_request(GET/POST/PATCH/PUT/DELETE).src/tools/util.ts—ok/fail, the four annotation presets (READ_ONLY/WRITE/UPDATE/DESTRUCTIVE), shared zod schema factories (personResourceNameSchema,personFieldsSchema, ...), thecontactFieldsShape()input factory andtoContactFields()(snake_case → normalized, no wire knowledge).src/index.ts— wires everyregister*into the McpServer.loadConfigOrDegraded()catchesConfigError, pingsstartup_failed(fire-and-forget) and degrades the config to "no credentials"; an unconfigured start prependsUNCONFIGURED_PREFIX— plusConfiguration problem: <message>when a ConfigError was caught — to the initializeinstructions, andoninitializedsendsserver_startfor a configured install orunconfigured_start(with the reason) otherwise.src/telemetry.ts— anonymous usage pings (ids/names/versions only, never data or arguments; fire-and-forget, must never block or throw; opt-outASKADS_TELEMETRY=0).server_startmeans "a usable install started";unconfigured_startis a degraded start andstartup_faileda malformed config caught at load — both carry areasonfrom a closed vocabulary (missing_credentials,incomplete_oauth_config) — never a variable's name or value.
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.
- 7d ago First seen · 141 lines · 2,436 tokens per session scan A cf7d341cc8eb
mcp-google-contacts CLAUDE.md is an instructions file published in the GitHub repository A1-x-Tech/mcp-google-contacts (0 stars, last pushed 9d ago), licensed MIT. It adds 2,436 tokens to every session, about $0.0122 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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 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).
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.