Borrowing it
Nothing to install: this file belongs to takumi0706/google-calendar-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/takumi0706/google-calendar-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/takumi0706/google-calendar-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/takumi0706/google-calendar-mcp/claude-md)<a href="https://agentmods.dev/instructions/takumi0706/google-calendar-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/takumi0706/google-calendar-mcp/claude-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/takumi0706/google-calendar-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/takumi0706/google-calendar-mcp/claude-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.00792 | $0.00792 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
google-calendar-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 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.
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.
This is a copy
83% identical to cc-sdd AGENTS.md — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SDLC and Spec-Driven Development
Kiro-style Spec-Driven Development on an agentic SDLC
Project Context
Paths
- Steering:
.kiro/steering/ - Specs:
.kiro/specs/
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
- Check
.kiro/specs/for active specifications - Use
/kiro-spec-status [feature-name]to check progress
Development Guidelines
- Think in English, generate responses in Japanese. All Markdown content written to project files (e.g., requirements.md, design.md, tasks.md, research.md, validation reports) MUST be written in the target language configured for this specification (see spec.json.language).
Minimal Workflow
- Phase 0 (optional):
/kiro-steering,/kiro-steering-custom - Discovery:
/kiro-discovery "idea"— determines action path, writes brief.md + roadmap.md for multi-spec projects - Phase 1 (Specification):
- Single spec:
/kiro-spec-quick {feature} [--auto]or step by step:/kiro-spec-init "description"/kiro-spec-requirements {feature}/kiro-validate-gap {feature}(optional: for existing codebase)/kiro-spec-design {feature} [-y]/kiro-validate-design {feature}(optional: design review)/kiro-spec-tasks {feature} [-y]
- Multi-spec:
/kiro-spec-batch— creates all specs from roadmap.md in parallel by dependency wave
- Single spec:
- Phase 2 (Implementation):
/kiro-impl {feature} [tasks]- Without task numbers: autonomous mode (subagent per task + independent review + final validation)
- With task numbers: manual mode (selected tasks in main context, still reviewer-gated before completion)
/kiro-validate-impl {feature}(standalone re-validation)
- Progress check:
/kiro-spec-status {feature}(use anytime)
Skills Structure
Skills are located in .claude/skills/kiro-*/SKILL.md
- Each skill is a directory with a
SKILL.mdfile - Skills run inline with access to conversation context
- Skills may delegate parallel research to subagents for efficiency
- Additional files (templates, examples) can be added to skill directories
kiro-review— task-local adversarial review protocol used by reviewer subagentskiro-debug— root-cause-first debug protocol used by debugger subagentskiro-verify-completion— fresh-evidence gate before success or completion claims- If there is even a 1% chance a skill applies to the current task, invoke it. Do not skip skills because the task seems simple.
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 · 62 lines · 792 tokens per session scan A 6055d283e896
google-calendar-mcp CLAUDE.md is an instructions file published in the GitHub repository takumi0706/google-calendar-mcp (59 stars, last pushed 24d ago), licensed MIT. It adds 792 tokens to every session, about $0.0040 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to cc-sdd AGENTS.md, differing in 6 lines, and is treated as a copy.
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).