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/ondrasek/cc-plugins/list-calendarsnpx skills add ondrasek/cc-plugins --skill list-calendarsgit clone --depth 1 https://github.com/ondrasek/cc-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/skills/ondrasek/cc-plugins/list-calendars)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/list-calendars"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/list-calendars.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.00049 | $0.00407 |
| Opus 5 | $0.00024 | $0.00204 |
| Sonnet 5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
list-calendars scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer $TOKEN" \ What it actually says
List Calendars
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Read-only — never create, modify, or delete calendars
Context Files
Read these files before starting:
skills/shared/references/cross-cutting.md— provider detection, error handlingskills/shared/references/providers.md— CLI commands for listing calendars
Workflow
1. Detect Providers
Follow provider detection from cross-cutting.md. Stop if no provider is available.
2. List Calendars
Google Calendar:
gcalcli list
Microsoft 365:
TOKEN=$(az account get-access-token --resource https://graph.microsoft.com --query accessToken -o tsv)
curl -s -H "Authorization: Bearer $TOKEN" \
"https://graph.microsoft.com/v1.0/me/calendars?\$select=name,color,isDefaultCalendar,canEdit"
3. Format Output
Present as a table grouped by provider:
## Calendars
### Google Calendar
| Calendar | Access |
|----------|--------|
| Personal | owner |
| Work | reader |
| Holidays in US | reader |
### Microsoft 365
| Calendar | Default | Color |
|----------|---------|-------|
| Calendar | Yes | Blue |
| Birthdays | No | Purple |
If only one provider is configured, omit the provider header grouping.
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.
- 4d ago First seen · 65 lines · 49 tokens per session scan A 4603cb4a44ce
list-calendars is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 407 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…