google-mcp: Instructions file for Claude Code

CLAUDE.md

google-mcp CLAUDE.md is an instructions file for Claude Code from nguyenvanduocit/google-mcp. It costs 693 tokens per session, scanned A, original, MIT.

Project instructions for building Google Chat features with a specification-first workflow. They explain how project-wide guidance and feature specifications are stored and how Claude Code commands track active work.

In plain words
What is it for?
It is for developing features such as retrieving Google Chat thread messages or user details, managing project guidance, and checking the status of active specifications.
Why use it?
Feature work can become inconsistent when requirements, project rules, and progress are kept in different places. These instructions give the agent a defined path from requirements to implementation.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code.

This is nguyenvanduocit/google-mcp's own configuration. It tells Claude Code how to work on google-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything google-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nguyenvanduocit/google-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nguyenvanduocit/google-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/nguyenvanduocit/google-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for google-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nguyenvanduocit/google-mcp/claude-md.svg)](https://agentmods.dev/instructions/nguyenvanduocit/google-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/nguyenvanduocit/google-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/nguyenvanduocit/google-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 693 This file is loaded in full into every session.
When invoked 693 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00693 $0.00693
Opus 5 $0.00347 $0.00347
Sonnet 5 $0.00139 $0.00139
Haiku 4.5 $0.00069 $0.00069

Measured 8d ago against content hash 987984d89cda, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d 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.

CLAUDE.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Code Spec-Driven Development

Kiro-style Spec Driven Development implementation using claude code slash commands, hooks and agents.

Project Context

Paths

  • Steering: .kiro/steering/
  • Specs: .kiro/specs/
  • Commands: .claude/commands/

Steering vs Specification

Steering (.kiro/steering/) - Guide AI with project-wide rules and context
Specs (.kiro/specs/) - Formalize development process for individual features

Active Specifications

  • get-thread-messages: Enable users to retrieve messages from Google Chat threads
  • get-user-info: Retrieve username and display name for Google Chat users
  • Check .kiro/specs/ for active specifications
  • Use /kiro:spec-status [feature-name] to check progress

Development Guidelines

  • Think in English, generate responses in English

Workflow

Phase 0: Steering (Optional)

/kiro:steering - Create/update steering documents
/kiro:steering-custom - Create custom steering for specialized contexts

Note: Optional for new features or small additions. You can proceed directly to spec-init.

Phase 1: Specification Creation

  1. /kiro:spec-init [detailed description] - Initialize spec with detailed project description
  2. /kiro:spec-requirements [feature] - Generate requirements document
  3. /kiro:spec-design [feature] - Interactive: "Have you reviewed requirements.md? [y/N]"
  4. /kiro:spec-tasks [feature] - Interactive: Confirms both requirements and design review

Phase 2: Progress Tracking

/kiro:spec-status [feature] - Check current progress and phases

Development Rules

  1. Consider steering: Run /kiro:steering before major development (optional for new features)
  2. Follow 3-phase approval workflow: Requirements → Design → Tasks → Implementation
  3. Approval required: Each phase requires human review (interactive prompt or manual)
  4. No skipping phases: Design requires approved requirements; Tasks require approved design
  5. Update task status: Mark tasks as completed when working on them
  6. Keep steering current: Run /kiro:steering after significant changes
  7. Check spec compliance: Use /kiro:spec-status to verify alignment

Read the full file on GitHub · 74 lines

Changes

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.

  1. 8d ago First seen · 74 lines · 693 tokens per session scan A 987984d89cda

Subscribe to this mod's changes

google-mcp CLAUDE.md is an instructions file published in the GitHub repository nguyenvanduocit/google-mcp (20 stars, last pushed 5mo ago), licensed MIT. It adds 693 tokens to every session, about $0.0035 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-30.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens