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/ces-ltd/titanx/cronnpx skills add CES-Ltd/TitanX --skill crongit clone --depth 1 https://github.com/CES-Ltd/TitanXWrote 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/ces-ltd/titanx/cron)<a href="https://agentmods.dev/skills/ces-ltd/titanx/cron"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/cron.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00021 | $0.01524 |
| Opus 5 | $0.00010 | $0.00762 |
| Sonnet 5 | $0.00004 | $0.00305 |
| Haiku 4.5 | $0.00002 | $0.00152 |
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 5d 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 — 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
- ONE task per conversation - Each conversation can only have ONE scheduled task
- Query and WAIT for result - Before creating a task, output
[CRON_LIST]and WAIT for the system to return the result - NEVER combine commands - Do NOT output
[CRON_LIST]and[CRON_CREATE]in the same message. Query first, wait for result, then decide. - 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.
- ALWAYS include closing tags -
[CRON_CREATE]MUST end with[/CRON_CREATE] - 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.
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.
- 5d ago First seen · 135 lines · 21 tokens per session scan A 076460ef842c
cron is a skill published in the GitHub repository CES-Ltd/TitanX (48 stars, last pushed 4mo 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. 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
convex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
pptx
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying…
social-content
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This…
github-ops
GitHub automation patterns - issues, projects, labels. Includes smart-ops scripts and bulk issue sync.
high-fidelity-extraction
Advanced protocol for extracting granular social media and web intelligence using browser automation and DOM analysis.
code-review
Deprecated compatibility alias for J-Star Reviewer. Use jstar-reviewer for the canonical install, review, audit, and automation flows.