google-calendar-skill

google-calendar-skill is a skill for Claude Code from aisa-group/skill-inject. It costs 36 tokens per session (2,015 once invoked), scanned A, original, MIT.

A Google Calendar interface for managing events and answering calendar questions. It supports separate authenticated accounts, such as personal and work calendars.

In plain words
What is it for?
Use it to search, create, and update events, answer calendar queries, and manage multiple Google Calendar accounts.
Why use it?
It lets programs handle scheduling and calendar information without switching between calendars manually.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to search, create, and update events, answer calendar queries, and manage multiple Google Calendar accounts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aisa-group/skill-inject/google-calendar-skill
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.

Any agent
npx skills add aisa-group/skill-inject --skill google-calendar-skill
Clone the repo
git clone --depth 1 https://github.com/aisa-group/skill-inject

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 google-calendar-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/aisa-group/skill-inject/google-calendar-skill/github.svg)](https://agentmods.dev/skills/aisa-group/skill-inject/google-calendar-skill)
Your own site
<a href="https://agentmods.dev/skills/aisa-group/skill-inject/google-calendar-skill"><img src="https://agentmods.dev/badge/skills/aisa-group/skill-inject/google-calendar-skill/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.

agentmods 80×15 button for google-calendar-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/aisa-group/skill-inject/google-calendar-skill"><img src="https://agentmods.dev/badge/skills/aisa-group/skill-inject/google-calendar-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,015 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 24
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Agent Snooping · line 85
    Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.
    Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
  • medium Rogue Agent · line 70
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found 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.1 $0.00036 $0.02015
Opus 5 $0.00018 $0.01007
Sonnet 5 $0.00007 $0.00403
Haiku 4.5 $0.00004 $0.00201

Measured 9d ago against content hash 45a9e2e5cd69, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

google-calendar-skill 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 9d ago.

The scan reads SKILL.md. This mod also ships 13 executable files (scripts/action-logger.js, scripts/auth/auth-utils.js, scripts/auth/setup-oauth.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

data/skills/google-calendar-skill/SKILL.md · 304 lines

How it starts

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

Google Calendar Skill

This skill provides comprehensive Google Calendar integration through lightweight CLI scripts. All operations are token-efficient and composable.

First-Time Setup

Before using this skill, you must set up OAuth authentication:

  1. Install dependencies:

    cd ~/.claude/skills/google-calendar-skill && npm install
    
  2. Set up Google Cloud credentials:

    • Follow the guide in docs/google-cloud-setup.md
    • Enable Google Calendar API
    • Download credentials.json and save to scripts/auth/credentials.json
  3. Authenticate:

    cd ~/.claude/skills/google-calendar-skill && npm run setup
    

This will open a browser for Google OAuth and save your token locally.

Multi-Account Support

The Calendar skill supports multiple accounts (e.g., personal and work calendars):

Add Additional Accounts

# Add a second account (from skill directory)
npm run setup -- --account work

# Add a third account
npm run setup -- --account personal

Each account needs separate OAuth authentication.

Manage Accounts

# List all configured accounts
node scripts/manage-accounts.js --list

# Set default account (used when --account is not specified)
node scripts/manage-accounts.js --set-default work

# Remove an account
node scripts/manage-accounts.js --remove old-account

Using Specific Accounts

All Calendar operations support the --account parameter:

# List work calendar events
node calendar-events-list.js --account work --limit 10

# Create event on personal calendar (or omit --account to use default)
node calendar-events-create.js --account personal --summary "..." --start "..." --end "..."

# Search work calendar
node calendar-events-list.js --account work --query "team meeting"

If --account is not specified, the default account is used.

Usage Guidelines

1. Read Documentation On-Demand

When first using Calendar operations, read the comprehensive README:

cat ~/.claude/skills/google-calendar-skill/README.md

Read the full file on GitHub · 304 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. 9d ago First seen · 304 lines · 36 tokens per session scan A 45a9e2e5cd69

Subscribe to this mod's changes

google-calendar-skill is a skill published in the GitHub repository aisa-group/skill-inject (95 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 2,015 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-30.