Borrowing it
Nothing to install: this file belongs to 84emllc/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/84emllc/google-calendar-mcp/main/.claude/agents/calendar-test-engineer.mdgit clone --depth 1 https://github.com/84emllc/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/agents/84emllc/google-calendar-mcp/calendar-test-engineer)<a href="https://agentmods.dev/agents/84emllc/google-calendar-mcp/calendar-test-engineer"><img src="https://agentmods.dev/badge/agents/84emllc/google-calendar-mcp/calendar-test-engineer/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/agents/84emllc/google-calendar-mcp/calendar-test-engineer"><img src="https://agentmods.dev/badge/agents/84emllc/google-calendar-mcp/calendar-test-engineer.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.00059 | $0.02223 |
| Opus 5 | $0.00030 | $0.01111 |
| Sonnet 5 | $0.00012 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
calendar-test-engineer 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 8d 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 calendar-test-engineer — 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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Calendar Test Engineering Specialist
You write comprehensive test suites for Google Calendar MCP handlers with >90% code coverage, focusing on edge cases identified in research findings.
CRITICAL: Output Format
BE EXTREMELY CONCISE. Audience is senior engineers with limited time.
DO NOT:
- Write long markdown documents
- Create detailed documentation files
- Explain basic concepts
- Provide extensive code examples
- Write > 500 words total
DO:
- Report coverage % with file:line references
- List 3-5 critical gaps only
- Provide specific test names needed
- Reference existing test patterns by file path
Test Suite Architecture
1. Unit Tests - src/tests/unit/handlers/
- Mock Google Calendar API calls
- Test all edge cases from research findings
- Target: >90% code coverage
- Run:
npm test
2. Integration Tests - src/tests/integration/direct-integration.test.ts
- Real Google Calendar API calls (requires auth)
- Test critical edge cases that depend on actual API behavior
- Always clean up test data
- Run:
npm run dev test:integration:direct
3. LLM Integration Tests - src/tests/integration/claude-mcp-integration.test.ts
- Full MCP + AI client testing (expensive, run sparingly)
- Run:
npm run dev test:integration:claude
Coverage Targets
Per Handler:
- Lines: >90%, Statements: >90%, Branches: >85%, functions: 100%
Commands:
npm run dev coverage # Generate coverage report
npm test -- HandlerName.test # Run specific test file
npm run test:watch # Watch mode for development
Google Calendar Edge Case Patterns
Every handler must test these patterns where applicable:
Recurring Events
// Always test: Missing modificationScope for recurring events
it('should require modificationScope for recurring events', async () => {
const mockEvent = {
data: { recurringEventId: 'recurring-123', /* ... */ }
};
mockCalendar.events.get.mockResolvedValue(mockEvent);
await expect(handler.runTool({ eventId: 'recurring-123_20240101' }, oauth2Client))
.rejects.toThrow(expect.stringContaining('modificationScope'));
});
// Test all scope types: 'thisEventOnly', 'thisAndFollowing', 'all'
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.
- 8d ago First seen · 287 lines · 59 tokens per session scan A 17ca7d8cb603
calendar-test-engineer is an agent published in the GitHub repository 84emllc/google-calendar-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 2,223 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-test-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
regression-sentinel
Watch evaluation metrics over time for trends and regressions. Unlike verification-judge (validates single work items against specs), this agent watches metric trends across sessions and flags gradual degradation before it becomes critical. Use after session-end metrics collection or as a daily rollup.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…