scheduler

A rule that converts natural-language recurring-task requests into a five-part cron schedule and a ready-to-send /schedule command. Cron is a format for describing when repeated jobs should run.

In plain words
What is it for?
Use it to register daily or recurring tasks, list scheduled jobs, remove them, or get scheduling help.
Why use it?
It prevents users from being sent to unsupported scheduling tools when the environment already provides a /schedule command.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/zhourong12/cursor-bridge/scheduler
Clone the repo
git clone --depth 1 https://github.com/zhourong12/cursor-bridge

Made for: Cursor.

Per session 285 This file is loaded in full into every session.
When invoked 285 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00285 $0.00285
Opus 5 $0.00143 $0.00143
Sonnet 5 $0.00057 $0.00057
Haiku 4.5 $0.00028 $0.00028

Measured 2d ago against content hash fb8ce6f56fb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/rules/scheduler.mdc · 28 lines

What it actually says

定时任务(/schedule)

当用户用自然语言要求定时 / 周期 / 每天几点执行某任务时:

  • 禁止回答「不支持定时」「没有 /cron」「要用 Windows 计划任务」——本 fork 已支持 /schedule
  1. 将时间转为 5 段 cron(分 时 日 月 周),例如每天 9:00 → 0 9 * * *
  2. 回复一条可直接发送的登记命令:
/schedule add <分> <时> <日> <月> <周> <任务描述>

示例:用户说「每天早上 9 点巡检代码」→ 回复:

/schedule add 0 9 * * * 巡检当前工作区代码并简要总结
  1. 说明:任务在 bridge 常驻运行时生效;结果会发回登记时的会话
  2. 查看:/schedule list;删除:/schedule remove <id>;帮助:/schedule help

不要编造不存在的 cron 工具;登记只靠 /schedule 命令。

Changes

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.

  1. 2d ago First seen · 28 lines · 285 tokens per session scan A fb8ce6f56fb9

Subscribe to this mod's changes

scheduler is a cursor rule published in the GitHub repository zhourong12/cursor-bridge (2 stars, last pushed 2mo ago), licensed MIT. It adds 285 tokens to every session, about $0.0014 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.