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.
git clone --depth 1 https://github.com/quinnjr/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/rules/quinnjr/google-mcp/typescript)<a href="https://agentmods.dev/rules/quinnjr/google-mcp/typescript"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/typescript/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/rules/quinnjr/google-mcp/typescript"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/typescript.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.00000 | $0.01149 |
| Opus 5.5 | $0.00000 | $0.00460 |
| Sonnet 5.5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
typescript 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 1mo 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Best Practices
Follow these conventions when writing TypeScript code in this project.
Type Safety
-
Avoid
any- Useunknownfor truly unknown types, then narrow with type guards// Bad function process(data: any) { ... } // Good function process(data: unknown) { if (typeof data === 'string') { ... } } -
Prefer explicit return types - Always declare return types on functions and methods
// Bad function getData() { return { id: 1 }; } // Good function getData(): { id: number } { return { id: 1 }; } -
Use strict null checks - Handle
nullandundefinedexplicitly// Bad const name = user.name.toUpperCase(); // Good const name = user.name?.toUpperCase() ?? 'Unknown';
Access Modifiers
All class members must have explicit access modifiers:
class MyService {
private readonly client: Client;
constructor(client: Client) {
this.client = client;
}
public async getData(): Promise<Data> { ... }
private validateInput(input: string): boolean { ... }
}
- Use
privatefor internal implementation details - Use
publicfor API surface - Use
protectedfor inheritance hierarchies - Use
readonlyfor immutable properties
Naming Conventions
| Type | Convention | Example |
|---|---|---|
| Classes | PascalCase | UserService |
| Interfaces | PascalCase | UserConfig |
| Type aliases | PascalCase | UserId |
| Enums | PascalCase | UserRole |
| Enum members | UPPER_CASE or PascalCase | ADMIN or Admin |
| Functions | camelCase | getUserById |
| Variables | camelCase | userCount |
| Constants | UPPER_SNAKE_CASE | MAX_RETRIES |
| Private members | camelCase (no underscore prefix) | private data |
Type Imports
Use type-only imports when importing types:
// Bad
import { User, UserService } from './user';
// Good
import { type User, UserService } from './user';
// or
import type { User } from './user';
import { UserService } from './user';
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.
- 1mo ago First seen · 208 lines · 0 tokens per session scan A a1906631f81f
typescript is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,149 tokens. 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 cursor rules, from other repositories
nextjs-tanstack-query-cursorrules-prompt-file
Cursor rules for Next.js App Router with TanStack Query v5, covering the HydrationBoundary pattern, Server Actions as mutations, and optimistic updates.
jest-unit-testing-cursorrules-prompt-file
Cursor rules for Jest development with unit testing.
nextjs-tanstack-query
Next.js App Router combined with TanStack Query v5 — HydrationBoundary pattern, Server Actions as mutations, optimistic updates, and infinite scroll.
nextjs-supabase-shadcn-pwa-cursorrules-prompt-file
Cursor rules for Nextjs Supabase Shadcn Pwa.
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
chrome-extension-dev-js-typescript-cursorrules-pro
Cursor rules for VSCode extension development with Electron and TypeScript integration.