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/last9/mithai/schedulingnpx skills add last9/mithai --skill schedulinggit clone --depth 1 https://github.com/last9/mithaiWhat 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.00000 | $0.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 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 2d 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.
- 2d ago First seen · 30 lines · 0 tokens per session scan A 3147cbf6209f
scheduling is a skill published in the GitHub repository last9/mithai (18 stars, last pushed 5d ago), 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
create-launch-post
Create and publish concise Rivet launch or changelog posts through an approval-gated workflow, including release research, a required user-selected hero variation, local HTML-rendered social and technical images, an R2 hero upload, MDX authoring, a reviewed draft GitHub PR for manual merge, and a scheduled and…
driver-test-runner
Methodically run the RivetKit driver test suite file by file across the native (NAPI) and wasm runtimes, tracking progress in /.agents/notes/driver-test-progress.md. Use when you need to validate the driver test suite after changes, bring up a new driver, or debug test failures systematically.
creating-docs-diagrams
Creates accessible hand-authored inline SVG architecture and sequence diagrams for documentation. Use when adding, replacing, or reviewing docs diagrams, especially Mermaid flowcharts.
stack-merge
Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says "merge the stack at ", "ship everything through ", "bulk-merge up to ", "fast-forward main to ", or any request to land multiple stacked PRs at once in one shot.…
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.