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/bug-ops/zeph/schedulernpx skills add bug-ops/zeph --skill schedulergit clone --depth 1 https://github.com/bug-ops/zephWhat 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.00076 | $0.01401 |
| Opus 5 | $0.00038 | $0.00700 |
| Sonnet 5 | $0.00015 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduler
Use schedule_periodic for recurring cron tasks, schedule_deferred for one-shot
tasks at a specific future time, and cancel_task to remove a scheduled task.
Create a daily memory cleanup (cron)
{"name": "daily-cleanup", "cron": "0 0 3 * * *", "kind": "memory_cleanup"}
Create a weekly skill refresh (cron)
{"name": "weekly-skill-refresh", "cron": "0 0 2 * * SUN", "kind": "skill_refresh"}
Run a custom task at a specific time (deferred)
{"name": "follow-up", "run_at": "2026-03-03T18:00:00Z", "kind": "custom", "task": "check if PR was merged and notify"}
{"name": "reminder-call-home", "run_at": "+2h", "kind": "custom", "task": "Remind the user to call home"}
{"name": "standup-reminder", "run_at": "in 30 minutes", "kind": "custom", "task": "Remind the user: standup in 5 minutes"}
{"name": "eod-summary", "run_at": "today 18:00", "kind": "custom", "task": "generate end-of-day summary"}
Cancel a scheduled task
{"name": "daily-cleanup"}
Cron Expression Reference
Both standard 5-field (min hour day month weekday) and 6-field (sec min hour day month weekday)
expressions are accepted. When 5 fields are given, seconds default to 0.
Field ranges
| Field | Position (6-field) | Allowed Values | Special Characters |
|---|---|---|---|
| Seconds | 1 | 0-59 | * , - / |
| Minutes | 2 | 0-59 | * , - / |
| Hours | 3 | 0-23 | * , - / |
| Day of Month | 4 | 1-31 | * , - / |
| Month | 5 | 1-12 or JAN-DEC | * , - / |
| Day of Week | 6 | 0-7 or SUN-SAT | * , - / |
Common cron examples
| Expression (6-field) | Meaning |
|---|---|
0 0 * * * * |
Every hour at :00 |
0 */15 * * * * |
Every 15 minutes |
0 0 3 * * * |
Daily at 03:00 |
0 30 9 * * MON-FRI |
Weekdays at 09:30 |
0 0 2 * * SUN |
Every Sunday at 02:00 |
0 0 0 1 * * |
First day of every month at midnight |
0 0 8,12,18 * * * |
At 08:00, 12:00, and 18:00 daily |
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 · 133 lines · 76 tokens per session scan A f26270949a29
scheduler is a skill published in the GitHub repository bug-ops/zeph (57 stars, last pushed 8d ago), licensed MIT. It adds 76 tokens to every session and 1,401 once invoked, about $0.0004 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-30.
Other skills, from other repositories
verify
Run Chimeraforge's canonical verification gate end-to-end and report the real output before claiming work done or committing. Failing output gets pasted, fixed, and re-run — never summarized away.
free-model-manager
Free AI model management - discover, download, and manage free/open-source AI models from Ollama, HuggingFace, and other sources.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.