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/xuiltul/animaworks/cron-managementnpx skills add xuiltul/animaworks --skill cron-managementgit clone --depth 1 https://github.com/xuiltul/animaworksWrote 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/xuiltul/animaworks/cron-management)<a href="https://agentmods.dev/skills/xuiltul/animaworks/cron-management"><img src="https://agentmods.dev/badge/skills/xuiltul/animaworks/cron-management.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.1 | $0.00040 | $0.03474 |
| Opus 5 | $0.00020 | $0.01737 |
| Sonnet 5 | $0.00008 | $0.00695 |
| Haiku 4.5 | $0.00004 | $0.00347 |
Grade A, and why
cron-management 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 6d 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cron.md Structure
Overall Structure
# Cron: {your_name}
## Task Name 1
schedule: 0 9 * * *
type: llm
Task description...
## Task Name 2
schedule: */5 * * * *
type: command
command: /path/to/script.sh
Rules You MUST Follow
- Each task must start with
## Task Name(H2 header. Do not use H3 or H1) schedule:line is required (must start withschedule:keyword. Not a###header)- Schedule must be standard 5-field cron expression only (
09:00orevery Friday 17:00are invalid) type:line is required (llmorcommand)- Insert blank lines between tasks (for readability)
Invalid Formats
❌ ### */5 * * * * ← Do NOT write cron expression as H3 header
❌ ### 09:00 ← Natural language time is invalid
❌ ### Every Friday 17:00 ← Natural language schedule is invalid
❌ cron: 0 9 * * * ← Key name must be "schedule:" (not "cron:")
❌ interval: 5m ← Interval format is invalid
❌ schedule: 0 9 * * * * ← 6 fields are invalid (5 fields only)
Valid Format
✅ schedule: 0 9 * * * ← "schedule:" + space + 5-field cron expression
✅ schedule: */5 * * * *
✅ schedule: 30 21 * * *
✅ schedule: 0 17 * * 5
5-Field Cron Expression Reference
Field Structure
schedule: minute hour day month weekday
| Field | Position | Range | Description |
|---|---|---|---|
| minute | 1 | 0-59 | Minute to execute |
| hour | 2 | 0-23 | Hour to execute (24-hour) |
| day | 3 | 1-31 | Day of month |
| month | 4 | 1-12 | Month |
| weekday | 5 | 0-6 | Day of week (0=Mon, 6=Sun) |
Note: Weekday is 0=Monday, 6=Sunday (APScheduler spec. Differs from standard cron where 0=Sunday)
Special Characters
| Char | Meaning | Example |
|---|---|---|
* |
All values | * * * * * = every minute |
*/n |
Every n | */5 * * * * = every 5 minutes |
n-m |
Range | 0 9-17 * * * = every hour 9am–5pm |
n,m |
List | 0 9,12,18 * * * = 9am, noon, 6pm |
n-m/s |
Range + step | 0 9-17/2 * * * = every 2 hours 9am–5pm |
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.
- 6d ago First seen · 389 lines · 40 tokens per session scan A 72027836ac93
cron-management is a skill published in the GitHub repository xuiltul/animaworks (254 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 3,474 once invoked, about $0.0002 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
email-triage
Classify incoming emails into triage categories using content analysis, sender profile memory, and thread detection. Produces a category (URGENT, REPLYNEEDED, FYI, NEWSLETTER, NOTIFICATION, SPAM) with confidence and reasoning.
open-questions
Shows the user dashboard: pending questions the agent has logged for the user, goals with participants including user, and blocked goals grouped by blocker reason. Use whenever the user says "what do you need from me", "what's blocked", "what questions do you have", "what am I on the hook for", or invokes…
efficient-execution
Reduce token waste and task completion time by choosing the simplest tool for each job.
local-document-organizer
Preview-first local file organizer. Scan a user-named folder, classify files with readable rules, show a plan, execute approved moves and undo them. Use for sorting Downloads, renaming into category folders, or reviewing organization history, including scoped metadata-only course persistence. Do not use for knowledge…
customer-email-assist
Review Gmail customer-support threads with a minimal-token, connector-first workflow. Use when Codex needs to read Gmail through the Codex Gmail connector, import cleaned messages into a local SQLite issue queue, apply deterministic cleanup and classification first, reserve model usage for JSON-only message…
personal-workflow-automation
Define, preview, execute and inspect manually triggered workflows with ordered deterministic tool steps and approval gates. Use for repeatable multi-step course routines and explicit retries. Do not use for file classification, knowledge synthesis, background scheduling or replacing another skill's work.