agentmods.dev

cron

cron is a skill for Claude Code, Codex from CES-Ltd/TitanX. It costs 21 tokens per session (1,524 once invoked), scanned A, original, Apache-2.0.

A guide for managing scheduled tasks that run operations automatically at specified times. It defines the required process for checking existing tasks, creating a task, and handling replacement or deletion.

In plain words
What is it for?
Use it to create, inspect, replace, or delete automated scheduled tasks while following the required confirmation and command format.
Why use it?
It prevents accidental duplicate schedules or deletion of an existing task. It also enforces a step-by-step workflow when task state or user confirmation matters.

Skill for Claude CodeCodex

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

not rated 49repo 6mo ago A scan 21 tokens original Apache-2.0

Good fit Use it to create, inspect, replace, or delete automated scheduled tasks while following the required confirmation and command format.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ces-ltd/titanx/cron
View source ↗ CES-Ltd/TitanX
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 CES-Ltd/TitanX --skill cron
Clone the repo
git clone --depth 1 https://github.com/CES-Ltd/TitanX

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/ces-ltd/titanx/cron/github.svg)](https://agentmods.dev/skills/ces-ltd/titanx/cron)
Your own site
<a href="https://agentmods.dev/skills/ces-ltd/titanx/cron"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/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/ces-ltd/titanx/cron"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,524 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.
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.00021 $0.01524
Opus 5.5 $0.00008 $0.00610
Sonnet 5.5 $0.00004 $0.00305
Haiku 4.5 $0.00002 $0.00152

Measured 2mo ago against content hash 076460ef842c, 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 2mo 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.

src/process/resources/skills/_builtin/cron/SKILL.md · 135 lines

How it starts

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

Scheduled Task Skill

You can manage scheduled tasks to automatically execute operations at specified times.

IMPORTANT RULES

  1. ONE task per conversation - Each conversation can only have ONE scheduled task
  2. Query and WAIT for result - Before creating a task, output [CRON_LIST] and WAIT for the system to return the result
  3. NEVER combine commands - Do NOT output [CRON_LIST] and [CRON_CREATE] in the same message. Query first, wait for result, then decide.
  4. ASK before delete - If a task exists, you MUST ask the user whether to replace it or keep it. NEVER delete without user's explicit confirmation.
  5. ALWAYS include closing tags - [CRON_CREATE] MUST end with [/CRON_CREATE]
  6. Output commands directly - Do NOT wrap commands in markdown code blocks

Workflow for Creating a Task

CRITICAL: This is a multi-turn workflow. Do NOT skip steps or combine them.

Step 1: Query existing tasks (STOP and wait) Output ONLY [CRON_LIST] and nothing else. The system will return the current task status. DO NOT proceed to Step 2 until you see the system response.

Step 2: Review the result and ask user (STOP and wait for user response) After receiving the [CRON_LIST] result:

  • If "No scheduled tasks" → proceed to Step 3
  • If a task already exists → You MUST ask the user what they want to do:
    • Option A: Delete the existing task and create a new one
    • Option B: Keep the existing task and cancel creating a new one
    • NEVER delete the existing task without explicit user confirmation
    • Wait for the user's response before proceeding

Step 3: Execute user's decision

  • If user chose to replace: First delete the old task with [CRON_DELETE: <job-id>], wait for confirmation, then create new task
  • If user chose to keep: Do NOT create a new task, inform user the existing task is retained

Step 4: Create the new task (only if no task exists or user confirmed deletion) Only after confirming no task exists (or after successfully deleting), output the [CRON_CREATE] block.

Read the full file on GitHub · 135 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. 2mo ago First seen · 135 lines · 21 tokens per session scan A 076460ef842c

Subscribe to this mod's changes

cron is a skill published in the GitHub repository CES-Ltd/TitanX (49 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,524 once invoked, about $0.0001 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.

Productivityagent-orchestrationai-agentsai-governanceaudit-loggingcopilotkitdesktop-app
Related

cron compared with skills from other repositories

cron next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
cronCES-Ltd/TitanXSkill496mo agoApache-2.0A21Claude Code, Codex
slackrunxhq/runxSkill104yesterdayApache-2.0A34Claude Code, Codex
attention-reviewrunxhq/runxSkill104yesterdayApache-2.0A25Claude Code, Codex
conversation-reviewrunxhq/runxSkill104yesterdayApache-2.0A30Claude Code, Codex
automation-architectFerroxLabs/waylandSkill6176d agoAGPL-3.0A90Claude Code, Codex
ai-automation-builderFerroxLabs/waylandSkill6176d agoAGPL-3.0A89Claude Code, Codex
ai-coding-assistant-power-userFerroxLabs/waylandSkill6176d agoAGPL-3.0A99Claude Code, Codex