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/fo0/clawstash/schedulernpx skills add fo0/clawstash --skill schedulergit clone --depth 1 https://github.com/fo0/clawstashWrote 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/fo0/clawstash/scheduler)<a href="https://agentmods.dev/skills/fo0/clawstash/scheduler"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/scheduler.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.00095 | $0.01951 |
| Opus 5 | $0.00048 | $0.00975 |
| Sonnet 5 | $0.00019 | $0.00390 |
| Haiku 4.5 | $0.00010 | $0.00195 |
Grade A, and why
scheduler 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduler — Routines, Loops and Cron Jobs
When to Use
- User says "/scheduler", "schedule this", "run this nightly/weekly", "every morning", "remind me in an hour", "check back later"
- The agent itself needs to come back later: waiting on CI, a long Docker build, a GHCR publish, a PR that is not ready yet
- A run is about to end and this session created triggers, cron jobs or PR subscriptions → the cleanup pass below is mandatory
Sub-commands (bare /scheduler routes by what the request asks for):
| Argument | Does |
|---|---|
list |
Every job visible from this surface — CronList, plus list_triggers where the MCP is present |
new |
Create one, after picking the layer in step 1 |
clean |
Run the cleanup contract now instead of at the end of the run |
1. Pick the layer by lifetime — this is the whole decision
| Need | Layer | How | Lifetime |
|---|---|---|---|
| Runs without this session, machine off, ≥ 1 h apart | Routine (cloud) | see Surfaces below | Durable, until deleted |
| Poll something while this session stays open | /loop or CronCreate |
/loop 10m <prompt> · /loop <prompt> (agent picks the interval) |
This session; recurring jobs expire after 7 days |
| One-off "come back to this later" inside the session | CronCreate one-shot |
or plain natural language ("in 45 minutes, check the tests") | This session; fires once, deletes itself |
| Needs local files / local tools on a schedule | Desktop scheduled task | user creates it in the Desktop app | Durable, machine must be on |
| React to an event instead of polling | not a scheduler | subscribe_pr_activity for PR events, a GitHub trigger on a routine, Monitor for a stream |
— |
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 · 102 lines · 95 tokens per session scan A 3b3ee1209763
scheduler is a skill published in the GitHub repository fo0/clawstash (1 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 1,951 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
@elad12390/web-research-assistant
Comprehensive MCP server for web research with 14 tools: SearXNG + Exa AI search, URL crawling, stealth scraping (Cloudflare bypass), package registry lookup (npm/PyPI/crates), GitHub stats, changelog fetching, tech comparison, error translation, API docs discovery, stock image search, and service health. Trigger…
business-model-validator
Use when a prospect, new customer, or existing operator wants to know whether Zooza fits their business, or which Zooza features map to how they operate. No Zooza account required — works as a pure knowledge interview.
spotify-mcp-doctor
Diagnose and repair NovaLux12/spotify-mcp-server failures — auth, permissions, devices, rate limits, OpenClaw wiring. Use when Spotify tool calls fail or setup stalls.
delegacion-local
Regla y catálogo para delegar pasos mecánicos (resumir, clasificar, extraer, boilerplate, mensaje de commit desde un diff, traducir texto o archivo, resumir salida de lint/tests/CI, explicar código, describir una imagen, verificar si el backend local está disponible) a modelos locales vía las tools local del MCP…
class-management
Use when the user wants to create a new class, group, or course in Zooza — e.g. "set up a Monday yoga class", "add a new group", "schedule a course". Guides through programme selection, venue, trainer, session pattern, and commits.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).