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.
curl -O https://raw.githubusercontent.com/nguyenvanduocit/google-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/nguyenvanduocit/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/nguyenvanduocit/google-mcp/claude-md)<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>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.00693 | $0.00693 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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.
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 threadsget-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
/kiro:spec-init [detailed description]- Initialize spec with detailed project description/kiro:spec-requirements [feature]- Generate requirements document/kiro:spec-design [feature]- Interactive: "Have you reviewed requirements.md? [y/N]"/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
- Consider steering: Run
/kiro:steeringbefore major development (optional for new features) - Follow 3-phase approval workflow: Requirements → Design → Tasks → Implementation
- Approval required: Each phase requires human review (interactive prompt or manual)
- No skipping phases: Design requires approved requirements; Tasks require approved design
- Update task status: Mark tasks as completed when working on them
- Keep steering current: Run
/kiro:steeringafter significant changes - Check spec compliance: Use
/kiro:spec-statusto verify alignment
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.
- 8d ago First seen · 74 lines · 693 tokens per session scan A 987984d89cda
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.
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.
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.
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.