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/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/calendar-sync)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/calendar-sync"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/calendar-sync/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/commands/gonzalezpazmonica/savia/calendar-sync"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/calendar-sync.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.00014 | $0.00265 |
| Opus 5.5 | $0.00006 | $0.00106 |
| Sonnet 5.5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
calendar-sync 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 20d 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.
This is a copy
100% identical to calendar-sync — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/calendar-sync — Sincronizar Calendario
Ejecutar skill: @.opencode/skills/smart-calendar/SKILL.md
Prerequisitos
GRAPH_CLIENT_IDyGRAPH_TENANT_IDconfigurados en pm-config.local.md- Token OAuth obtenido (device code flow o browser)
- Permisos:
Calendars.ReadWrite,MailboxSettings.Read
Flujo
- Autenticar con Microsoft Graph (device code flow si primera vez)
- Leer eventos del calendario (default: proximos 7 dias)
- Sincronizar con estado local:
data/calendar-cache.json - Detectar conflictos: reuniones superpuestas, sin agenda, en horario no laboral
- Mostrar resumen: reuniones, huecos, % capacidad productiva
Banner
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 /calendar-sync — Sincronizacion Outlook
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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.
- 20d ago Changed 704442222e9b
- 1mo ago First seen · 36 lines · 14 tokens per session scan A 4ae4b547841a
calendar-sync is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 265 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to calendar-sync, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
show-your-work
Keep a reviewable TSV decision trail for long-running or unattended work. Usage: /show-your-work [task-slug].
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
project-stage-detect
Detect project phase and recommend actions.
sprint-plan
Generate or update sprint plan.
start
First-time onboarding — guided setup.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.