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 skills add shibing624/agentica --skill crongit clone --depth 1 https://github.com/shibing624/agenticaWrote 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/shibing624/agentica/cron)<a href="https://agentmods.dev/skills/shibing624/agentica/cron"><img src="https://agentmods.dev/badge/skills/shibing624/agentica/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.
<a href="https://agentmods.dev/skills/shibing624/agentica/cron"><img src="https://agentmods.dev/badge/skills/shibing624/agentica/cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00052 | $0.00610 |
| Opus 5.5 | $0.00021 | $0.00244 |
| Sonnet 5.5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled jobs
Use the cronjob tool. Do not edit crontab or ~/.agentica/cron/jobs.json by
hand. The tool schema lists the actions; do not invent them.
A job runs in a fresh session with none of this conversation. The prompt must be self-contained: goal, constraints, where things are, what to do when blocked. A prompt that needs a follow-up question will stall unattended.
Waiting on something this session started? Not cron.
To learn when a training run, eval, build, or any tmux/nohup job finishes,
do not schedule a minute-level poll. Start a read-only watcher with
execute(background=True) that loops on the job's exit marker (see the
execute tool's tmux/nohup notes). It spends no tokens while it waits, and
its exit comes back to this session as a new message.
A cron monitor costs a full agent run per tick and cannot reach this session: one production job polled a 37-hour training run every 6 minutes, 400+ times, and kept polling for four days after the run had ended.
Cron is for work that must recur on a clock or outlive this session.
If a job watches for an end state, it must stop itself
Write the exit condition into the prompt: "when <marker> exists (or the
process is gone), report the result and pause this job (its own id) with the
cronjob tool". Without it the job keeps firing after there is nothing left to
watch.
A job's agent has the CLI's file, shell, web, memory and cronjob tools, and
no session of its own. It has no list_agents / send_message /
ask_user_question: do not write a prompt that tells it to message a session
or ask the user.
Jobs only fire on their schedule while the scheduler daemon is on. How the user turns it on depends on the surface:
- Interactive CLI: they type
/cron daemon on. You cannot type slash commands; tell them which one./cronis also their surface for list / add / pause / run. - Gateway and other surfaces:
cron.enabledinconfig.yamlis a deployment-level setting. You cannot toggle it from this conversation; tell the user to ask whoever manages this deployment to enable it.
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.
- yesterday Changed · +26 lines ff87d23622b8
- 1mo ago First seen · 30 lines · 52 tokens per session scan A bba5e1a93c7b
cron is a skill published in the GitHub repository shibing624/agentica (357 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 610 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
automation
Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.
notes
Instructions for managing personal notes through a notes service, including searching, reading, creating, and appending to notes.
computer-use
Read and drive native desktop apps through the accessibility layer — list apps, snapshot a window as a numbered element tree, then click/type/scroll/drag by element index or screen coordinates. Use for a desktop app, not a web page. macOS + Windows; off unless enabled in Settings.
meetings
Context for the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks and calendar cache live, what the lifecycle states mean, how the app's agents are driven. Load when asked about a meeting's notes or action items, or when touching the meetings app data dir.
slack-summary
Distill a Slack channel or thread into actionable summary.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.