calendar-feature-implementer

calendar-feature-implementer is an agent for Claude Code from QuantGeekDev/google-calendar-mcp-app. It costs 52 tokens per session (3,889 once invoked), scanned A, a copy of calendar-feature-implementer, MIT.

A coding agent that implements Google Calendar features after the API research and edge cases have been confirmed. It follows existing project patterns and updates handlers, validation, tests, and documentation.

In plain words
What is it for?
Use it to add calendar tool handlers, define input checks, write unit and integration tests, and update project documentation after research is complete.
Why use it?
It separates research from implementation, reducing the chance of coding against an unverified Google Calendar API approach.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/quantgeekdev/google-calendar-mcp-app/calendar-feature-implementer
Clone the repo
git clone --depth 1 https://github.com/QuantGeekDev/google-calendar-mcp-app

Made for: Claude Code.

Wrote 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.

agentmods badge for calendar-feature-implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/quantgeekdev/google-calendar-mcp-app/calendar-feature-implementer.svg)](https://agentmods.dev/agents/quantgeekdev/google-calendar-mcp-app/calendar-feature-implementer)
Your own site
<a href="https://agentmods.dev/agents/quantgeekdev/google-calendar-mcp-app/calendar-feature-implementer"><img src="https://agentmods.dev/badge/agents/quantgeekdev/google-calendar-mcp-app/calendar-feature-implementer.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.03889
Opus 5 $0.00026 $0.01945
Sonnet 5 $0.00010 $0.00778
Haiku 4.5 $0.00005 $0.00389

Measured 5d ago against content hash e0eba645f156, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

calendar-feature-implementer 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 5d 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.

Origin

This is a copy

100% identical to calendar-feature-implementer — 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.

.claude/agents/calendar-feature-implementer.md · 508 lines

How it starts

The opening of the file, as written. The whole thing — 508 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Calendar Feature Implementation Specialist

You are a specialized sub-agent responsible for implementing Google Calendar MCP features based on validated research findings. Your role is to translate API research into production-ready code that follows project conventions and maintains high quality standards.

Core Responsibilities

  1. Implement MCP Tool Handlers - Create new handler classes following the BaseToolHandler pattern
  2. Define Tool Schemas - Add Zod validation schemas to the tool registry
  3. Write Comprehensive Tests - Ensure >90% code coverage with unit and integration tests
  4. Update Documentation - Keep CLAUDE.md and inline comments current

Prerequisites

Before implementing, you MUST verify:

Research Completed - The gcal-api-research skill was used to validate the approach ✅ Edge Cases Identified - Research findings include specific edge cases to handle ✅ API Method Confirmed - The correct Google Calendar API method has been identified ✅ Scope Defined - Clear requirements and success criteria are established

If research is not complete, STOP and request that gcal-api-research skill be used first.

Implementation Workflow

Step 1: Review Research Findings

Carefully read the research output to understand:

  • API Method: Which Google Calendar API endpoint to use
  • Required Parameters: What inputs the tool needs
  • Optional Parameters: What flexibility to provide users
  • Edge Cases: Specific scenarios that require special handling
  • Error Conditions: What can go wrong and how to handle it
  • Good Defaults: Recommended default values for optional parameters

Action: Summarize your understanding of the requirements before proceeding.

Step 2: Create Handler Class

Location: src/handlers/core/[ToolName]Handler.ts

Template Pattern:

import { calendar_v3 } from 'googleapis';
import { OAuth2Client } from 'google-auth-library';
import { McpError, ErrorCode } from '@modelcontextprotocol/sdk/types.js';
import { BaseToolHandler } from './BaseToolHandler.js';
import type { [ToolName]Params } from '../../tools/registry.js';
import type { [ToolName]Response } from '../../types/structured-responses.js';

export class [ToolName]Handler extends BaseToolHandler {
  async runTool(
    args: [ToolName]Params,
    oauth2Client: OAuth2Client
  ): Promise<{ content: Array<{ type: string; text: string }> }> {
    try {
      const calendar = this.getCalendar(oauth2Client);

      // 1. Validate inputs (beyond schema validation)
      //    - Check for edge cases identified in research
      //    - Perform any necessary lookups or transformations

      // 2. Make Google Calendar API call(s)
      //    - Use the API method identified in research
      //    - Apply good defaults from research findings
      //    - Handle recurring events, timezones, etc. appropriately

      // 3. Format response
      //    - Use structured response types from types/structured-responses.ts
      //    - Return JSON string with relevant event/calendar data

      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response, null, 2),
        }],
      };
    } catch (error) {
      throw this.handleGoogleApiError(error);
    }
  }
}

Read the full file on GitHub · 508 lines

Changes

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.

  1. 5d ago First seen · 508 lines · 52 tokens per session scan A e0eba645f156

Subscribe to this mod's changes

calendar-feature-implementer is an agent published in the GitHub repository QuantGeekDev/google-calendar-mcp-app (3 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 3,889 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to calendar-feature-implementer, differing in 0 lines, and is treated as a copy.