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 last9/mithai --skill schedulinggit clone --depth 1 https://github.com/last9/mithaiWrote 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/last9/mithai/scheduling)<a href="https://agentmods.dev/skills/last9/mithai/scheduling"><img src="https://agentmods.dev/badge/skills/last9/mithai/scheduling/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/last9/mithai/scheduling"><img src="https://agentmods.dev/badge/skills/last9/mithai/scheduling.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.00000 | $0.00286 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
scheduling 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
You can schedule recurring tasks that trigger yourself via cron + Slack.
How it works
When you create a schedule, a cron job posts a message mentioning you in the specified Slack channel. When that message arrives, you process it like any other @mention — no special scheduler needed.
When to use scheduling
- Recurring tasks: EOD summaries, morning health checks, weekly digests
- Periodic monitoring: check a service every N hours and report
- Reminders: nudge the team about standups, deployments, reviews
When NOT to use scheduling
- One-time tasks — just do them now
- Tasks that need sub-minute precision — cron's minimum is 1 minute
- Tasks that don't need your reasoning — use a plain cron + script instead
Tips
- Use
list_schedulesto see what's already scheduled before creating duplicates - Use descriptive labels so you can find and remove schedules later
- Cron expressions are in the system timezone — confirm with the user if needed
- Channel ID is required (not channel name). Ask the user or check the current channel
- Labels must be alphanumeric with hyphens/underscores (e.g.
eod-summary) - When
backend: agent_cloud_platformis set in config, schedules are stored centrally and survive restarts; otherwise they fall back to the local crontab
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 30 lines · 0 tokens per session scan A 3147cbf6209f
scheduling is a skill published in the GitHub repository last9/mithai (20 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 286 tokens. 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
media-workflow
Chain several vg generate steps into one production — ads, product shots, restorations, talking heads, try-ons, scored or subtitled video — when no single endpoint does the job.
model-catalog
Pick a vg generate endpoint for a task, and the default endpoint IDs the media skills use when none is named.
siyuan
SiYuan Note API for searching, reading, creating, and managing blocks and documents in a self-hosted knowledge base via curl.
agentmail
Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. [email protected]).
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
computer-use
Drive the user's desktop in the background — clicking, typing, scrolling, dragging — without stealing the cursor, keyboard focus, or switching virtual desktops / Spaces. Cross-platform: macOS, Windows, Linux. Works with any tool-capable model. Load this skill whenever the computeruse tool is available.