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.
npx agentmods add agents/quantgeekdev/google-calendar-mcp-app/calendar-test-engineergit 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/agents/quantgeekdev/google-calendar-mcp-app/calendar-test-engineer)<a href="https://agentmods.dev/agents/quantgeekdev/google-calendar-mcp-app/calendar-test-engineer"><img src="https://agentmods.dev/badge/agents/quantgeekdev/google-calendar-mcp-app/calendar-test-engineer.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 | $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 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.
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.
- 5d ago First seen · 287 lines · 59 tokens per session scan A 17ca7d8cb603
calendar-test-engineer is an agent published in the GitHub repository QuantGeekDev/google-calendar-mcp-app (3 stars, last pushed 5mo 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
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.