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 skills add itseffi/agentic-os --skill schedule-checkgit clone --depth 1 https://github.com/itseffi/agentic-osWrote 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/itseffi/agentic-os/schedule-check)<a href="https://agentmods.dev/skills/itseffi/agentic-os/schedule-check"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/schedule-check/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/skills/itseffi/agentic-os/schedule-check"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/schedule-check.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.00024 | $0.00410 |
| Opus 5.5 | $0.00010 | $0.00164 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
calendar-schedule-check 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 1mo 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
Calendar Schedule Check
Check today's calendar and factor meetings into daily planning.
Instructions
Step 1: Fetch Today's Events
Call calendar_list_events for today's date range.
Step 2: Categorize Events
Group events by type:
- Meetings - Events with other attendees
- Focus blocks - Solo blocked time
- External - Events outside work calendar
Step 3: Calculate Available Time
Today's Schedule:
09:00-10:00 Team standup (meeting)
11:00-12:00 1:1 with Sarah (meeting)
14:00-15:00 Focus time (blocked)
Available for deep work:
- 10:00-11:00 (1 hour)
- 12:00-14:00 (2 hours)
- 15:00-17:00 (2 hours)
Total: 5 hours available
Step 4: Factor into Task Planning
When recommending tasks:
- Match task estimated_time to available slots
- Prioritize P0/P1 tasks for longer blocks
- Suggest quick tasks for short gaps
Step 5: Offer Calendar Actions
| Option | Description |
|---|---|
| Block time | Reserve time for specific task |
| Reschedule | Move a meeting if needed |
| Continue | Proceed with task planning |
Example Flow
User: "What should I work on today?"
Agent:
- Checks calendar
- "You have 3 meetings today, 5 hours free..."
- Shows schedule overview
- Recommends tasks that fit available time
- Offers to block time for priority tasks
Notes
- Respect existing focus blocks
- Consider meeting prep time
- Account for lunch/breaks
- Warn if schedule is overloaded
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.
- 1mo ago First seen · 72 lines · 24 tokens per session scan A 842623c65d48
calendar-schedule-check is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 410 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
daily-standup-journal
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
getting-started
Interactive post-onboarding tour that adapts to whatever data exists (calendar, Granola, or none). Use right after onboarding, or when the user says 'show me around', 'how do I start'. Also use proactively when the vault is < 7 days old. Not for the initial setup itself; use setup.
resume-builder
Build resume and LinkedIn profile through guided interview.
dex-obsidian-setup
Turn on Obsidian mode and migrate the vault to wiki links. Use when the user says 'I use Obsidian', 'enable wiki links', 'make this work in Obsidian'. Not for connecting an external tool/API; use create-mcp/integrate-mcp.