Borrowing it
Nothing to install: this file belongs to jakub-lapinski/google-calendar-mcp-serviceaccount. 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/jakub-lapinski/google-calendar-mcp-serviceaccount/main/AGENTS.mdgit clone --depth 1 https://github.com/jakub-lapinski/google-calendar-mcp-serviceaccountWrote 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/jakub-lapinski/google-calendar-mcp-serviceaccount/agents-md)<a href="https://agentmods.dev/instructions/jakub-lapinski/google-calendar-mcp-serviceaccount/agents-md"><img src="https://agentmods.dev/badge/instructions/jakub-lapinski/google-calendar-mcp-serviceaccount/agents-md/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/instructions/jakub-lapinski/google-calendar-mcp-serviceaccount/agents-md"><img src="https://agentmods.dev/badge/instructions/jakub-lapinski/google-calendar-mcp-serviceaccount/agents-md.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.01179 | $0.01179 |
| Opus 5 | $0.00589 | $0.00589 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade B, and why
google-calendar-mcp-serviceaccount AGENTS.md scanned grade B with 1 finding 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
restrictive permissions (`chmod 600` on Unix). Never commit it. How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions: installing this MCP server
This file is for an AI coding agent helping a human install and configure this repo. Follow it in order. Steps are marked HUMAN (must be done by the person, in their browser — you cannot do these) or AGENT (you do these once the human has provided what the HUMAN steps produce).
1. Google Cloud service account — HUMAN
As of this writing, every step below is free — no billing account or credit card needs to be attached to the Google Cloud project. Tell the human this up front; it's a common point of hesitation. This could change in the future, so don't state it as a permanent guarantee if you're reading this much later than it was written.
The human must:
- Go to console.cloud.google.com and create a project (any name).
- Enable the Google Calendar API for that project.
- Go to Credentials → Create Credentials → Service Account (not "OAuth client ID" — this repo does not use OAuth).
- Open the created service account → Keys tab → Add Key → Create new key →
type JSON. This downloads a
.jsonfile. - Open Google Calendar, go to the settings of the calendar to use → "Share
with specific people" → add the service account's email address (shown
on its details page, looks like
[email protected]) → permission "Make changes to events".
Ask the human to give you the downloaded JSON file (its contents, or its
path if they place it on the target machine themselves) and the ID of the
calendar they shared. For someone's own primary calendar, the ID is simply
their email address (e.g. [email protected]) — this is not a placeholder,
it is the literal, correct value. For any other calendar (a secondary or
shared one), the ID is a generated string, found on that calendar's
Settings page under "Integrate calendar" → "Calendar ID" (often ending in
@group.calendar.google.com). Ask which calendar they shared and get the
exact ID from them — do not assume it is primary, and do not guess.
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.
- 11d ago First seen · 102 lines · 1,179 tokens per session scan B 6d176e9b4c60
google-calendar-mcp-serviceaccount AGENTS.md is an instructions file published in the GitHub repository jakub-lapinski/google-calendar-mcp-serviceaccount (1 stars, last pushed 20d ago), licensed MIT. It adds 1,179 tokens to every session, about $0.0059 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
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.
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).