Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add reggiechan74/cc-plugins/plugin install google-workspace-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/skills/reggiechan74/cc-plugins/authenticate)<a href="https://agentmods.dev/skills/reggiechan74/cc-plugins/authenticate"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/authenticate/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/skills/reggiechan74/cc-plugins/authenticate"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/authenticate.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.00036 | $0.00435 |
| Opus 5.5 | $0.00014 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
authenticate 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 1mo 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.
What it actually says
Google Workspace Authentication
Authenticate the Gmail and Google Calendar MCP servers via OAuth 2.0.
Prerequisites
- A Google Cloud Platform project with a Desktop-type OAuth 2.0 Client ID
- Download the OAuth JSON and place it in BOTH locations:
~/.gmail-mcp/gcp-oauth.keys.json~/.calendar-mcp/gcp-oauth.keys.json
- Enable these APIs in the GCP project:
- Gmail API
- Google Calendar API
- People API (for contact lookup)
Procedure
-
Verify OAuth keys exist:
ls ~/.gmail-mcp/gcp-oauth.keys.json ~/.calendar-mcp/gcp-oauth.keys.json -
Create config directories if missing:
mkdir -p ~/.gmail-mcp ~/.calendar-mcp -
Authenticate Gmail server (opens browser for OAuth consent):
node ${CLAUDE_PLUGIN_ROOT}/servers/gmail/index.js auth -
Authenticate Calendar server:
node ${CLAUDE_PLUGIN_ROOT}/servers/calendar/index.js auth -
Verify credentials were created:
ls ~/.gmail-mcp/credentials.json ~/.calendar-mcp/credentials.json -
Test connectivity by running
/mcpto reconnect both servers. -
Report success/failure to user.
Troubleshooting
- Port 3000 conflict:
lsof -ti:3000 | xargs kill -9then retry - Browser doesn't open: Copy the auth URL from terminal output manually
- People API error: Ensure People API is enabled in GCP console
- Token expired: Re-run this authentication flow. Tokens auto-refresh during normal use but may expire after prolonged inactivity.
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.
- 1mo ago First seen · 58 lines · 36 tokens per session scan A b0ffa93e0b34
authenticate is a skill published in the GitHub repository reggiechan74/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 435 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.