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 skills/reggiechan74/cc-plugins/authenticatenpx skills add reggiechan74/cc-plugins --skill authenticategit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWhat 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.00036 | $0.00435 |
| Opus 5 | $0.00018 | $0.00217 |
| Sonnet 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 2d 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.
- 2d ago First seen · 58 lines · 36 tokens per session scan A b0ffa93e0b34
authenticate is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 435 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.