cron

cron is a skill for Claude Code, Codex from HKUDS/nanobot. It costs 8 tokens per session (646 once invoked), scanned A, original, MIT.

A scheduler for sending reminders or running recurring tasks at specified times or intervals.

In plain words
What is it for?
Scheduling direct reminders, recurring agent tasks, and one-time tasks, as well as listing or removing scheduled jobs.
Why use it?
It prevents one-time reminders and repeated work from being forgotten or handled manually each time.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Scheduling direct reminders, recurring agent tasks, and one-time tasks, as well as listing or removing scheduled jobs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hkuds/nanobot/cron
About the project

nanobot is a small, self-hosted personal AI agent framework written in Python, providing an agent runtime that can operate through a WebUI, terminal, or chat applications. Users use it to connect language models with tools, memory, MCP integrations, scheduled automation, and multi-agent workflows. The catalogue add-ons provide skills and instructions for working with nanobot.

HKUDS/nanobot · 49,254 stars · on GitHub · nanobot.wiki

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.

Any agent
npx skills add HKUDS/nanobot --skill cron
Clone the repo
git clone --depth 1 https://github.com/HKUDS/nanobot

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cron

README.md
[![agentmods](https://agentmods.dev/badge/skills/hkuds/nanobot/cron/github.svg)](https://agentmods.dev/skills/hkuds/nanobot/cron)
Your own site
<a href="https://agentmods.dev/skills/hkuds/nanobot/cron"><img src="https://agentmods.dev/badge/skills/hkuds/nanobot/cron/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.

agentmods 80×15 button for cron

Your own site · 80×15
<a href="https://agentmods.dev/skills/hkuds/nanobot/cron"><img src="https://agentmods.dev/badge/skills/hkuds/nanobot/cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 646 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00008 $0.00646
Opus 5.5 $0.00003 $0.00258
Sonnet 5.5 $0.00002 $0.00129
Haiku 4.5 $0.00001 $0.00065

Measured 15d ago against content hash ab6bae1889b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cron 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 15d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • cron — 100% identical, 14 lines differ
nanobot/skills/cron/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cron

Use the cron tool to schedule reminders or recurring tasks. New tasks run in the current chat. nanobot sends the agent's final reply to that chat. The user can change the task's chat in WebUI.

Write what to do in message. For a normal reminder or report, do not copy the current channel, chat ID, or instructions to call the message tool into the task. For example, use "Remind me to drink water", not "Call message to send to this chat".

If the user asks to send to other chats, preserve those recipients in the task instructions. Use the message tool for those sends and for file attachments. Existing tasks that explicitly request a message call still use it; changing the task's chat does not change explicit recipients in its instructions.

Choose by timing and notification behavior, not repetition. A specified time or interval uses cron, even when it repeats: "every day at 8am, remind me to drink water" is a cron task. Use HEARTBEAT.md for background checks with flexible timing that should notify only on actionable changes. Heartbeat does not guarantee a requested time or interval; do not substitute it for an explicit schedule.

Task Types

  1. Reminder - the agent replies with the reminder when the task runs
  2. Task - the agent follows the instructions and replies with the result
  3. One-time - runs once at a specific time, then auto-deletes

Examples

Fixed reminder:

cron(action="add", message="Time to take a break!", every_seconds=1200)

Dynamic task (agent executes each time):

cron(action="add", message="Check HKUDS/nanobot GitHub stars and report", every_seconds=600)

One-time scheduled task (compute ISO datetime from current time):

cron(action="add", message="Remind me about the meeting", at="<ISO datetime>")

Timezone-aware cron:

cron(action="add", message="Morning standup", cron_expr="0 9 * * 1-5", tz="America/Vancouver")

List/remove:

cron(action="list")
cron(action="remove", job_id="abc123")

Read the full file on GitHub · 64 lines

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. 15d ago Changed · +4 lines ab6bae1889b2
  2. 1mo ago First seen · 60 lines · 8 tokens per session scan A 5f050ee98a94

Subscribe to this mod's changes

cron is a skill published in the GitHub repository HKUDS/nanobot (49,254 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 646 once invoked, about $0.0000 per session on Opus 5.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.