Borrowing it
Nothing to install: this file belongs to QuantGeekDev/google-calendar-mcp-app. 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/QuantGeekDev/google-calendar-mcp-app/main/.claude/commands/research-calendar-api.mdgit clone --depth 1 https://github.com/QuantGeekDev/google-calendar-mcp-appWrote 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/commands/quantgeekdev/google-calendar-mcp-app/research-calendar-api)<a href="https://agentmods.dev/commands/quantgeekdev/google-calendar-mcp-app/research-calendar-api"><img src="https://agentmods.dev/badge/commands/quantgeekdev/google-calendar-mcp-app/research-calendar-api.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.00017 | $0.00330 |
| Opus 5 | $0.00009 | $0.00165 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
research-calendar-api 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 6d 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
100% identical to research-calendar-api — 0 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.
What it actually says
Use the gcal-api-research skill to conduct thorough research on: $ARGUMENTS
Research Focus Areas
Investigate the following aspects:
- Best API Approach - Identify the correct Google Calendar API method(s) to use
- Edge Cases - Uncover potential pitfalls and gotchas specific to this feature
- Community Issues - Find real-world problems others have encountered
- Best Practices - Validate the approach against Google's recommendations
- Implementation Complexity - Assess the effort required and any API limitations
Expected Output
Provide actionable research findings that include:
- ✅ Recommended API method and implementation approach
- ⚠️ Critical edge cases that must be handled
- 📋 Specific code patterns and parameter recommendations
- 🧪 Testing scenarios to validate the implementation
- 📚 References to official documentation and community resources
Research Workflow
Follow the gcal-api-research skill's structured workflow:
- Understand the feature requirements
- Consult reference materials (research-checklist.md, api-patterns.md, edge-cases.md)
- Fetch official Google Calendar API documentation
- Search for community-reported issues (Stack Overflow, GitHub)
- Validate implementation approach
- Provide clear, actionable findings
Focus on recurring events, timezone handling, batch operations, and multi-calendar support where applicable.
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.
- 6d ago First seen · 41 lines · 17 tokens per session scan A 2cf2fe919db0
research-calendar-api is a command published in the GitHub repository QuantGeekDev/google-calendar-mcp-app (3 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 330 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to research-calendar-api, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
Command "start-10-1" from minicoohei/ai-agent-camp, covering 🎓 lesson 10-1: clasp基本・gasプロジェクト管理, 📍 このセッションでやること, 🎯 準備チェック, 🚀 step 1: claspのインストールと apps script api の確認 and 🚀 step 2: google認証.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…