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.
git clone --depth 1 https://github.com/fiale-plus/fiale-claude-pluginsWrote 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/commands/fiale-plus/fiale-claude-plugins/hub-setup-gcalendar)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/hub-setup-gcalendar"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/hub-setup-gcalendar.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.1 | $0.00013 | $0.00371 |
| Opus 5 | $0.00006 | $0.00186 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
hub-setup-gcalendar 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.
What it actually says
/hub-setup-gcalendar
Set up Google Calendar API integration for Status Hub.
Usage
/hub-setup-gcalendar
When to Use
Use this command when:
- You want calendar alerts without keeping a browser tab open
- You're in a headless or remote environment without Chrome MCP
- You prefer API access over browser DOM scraping
What It Does
This command walks you through:
- Creating OAuth2 credentials in Google Cloud Console (if needed)
- Authorizing access to your Google Calendar
- Storing credentials securely in
~/.claude/ - Verifying the connection works
Prerequisites
- A Google account
- Access to Google Cloud Console (free)
- Ability to enable APIs and create OAuth credentials
After Setup
Once configured, your statusline will show upcoming meetings and you can use /hub-ack to:
- Join meetings directly
- Send "running late" messages
- Dismiss alerts
Switching Connection Methods
The hub supports two calendar connection methods:
| Method | Config Value | Pros | Cons |
|---|---|---|---|
| API | "api" |
Works without browser, headless-friendly | Requires OAuth setup |
| Chrome | "chrome" |
No API setup needed | Requires browser tab open |
To switch, edit ~/.claude/status-config.json:
{
"calendar": {
"connection": "api" // or "chrome"
}
}
See Also
/hub-setup- Main hub configuration/hub-ack- Acknowledge alerts including calendar/hub- View current hub status
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 · 66 lines · 13 tokens per session scan A 5104722accd7
hub-setup-gcalendar is a command published in the GitHub repository fiale-plus/fiale-claude-plugins (4 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 371 once invoked, about $0.0001 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 commands, from other repositories
migration-observability
Migration monitoring, CDC, and observability infrastructure.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
gws-people
Search and look up Google Contacts and directory profiles.
check
Run a quick scan of the memory system's health. For daily use.