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 commands/dmzoneill/redhat-ai-workflow/crongit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWrote 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/commands/dmzoneill/redhat-ai-workflow/cron)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/cron"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/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.00000 | $0.02101 |
| Opus 5 | $0.00000 | $0.01051 |
| Sonnet 5 | $0.00000 | $0.00420 |
| Haiku 4.5 | $0.00000 | $0.00210 |
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 3d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🕐 Cron Scheduler
Schedule skills to run automatically at specific times or based on events.
Overview
The cron scheduler allows you to automate recurring tasks like:
- Morning briefings (
/coffee) at 8:30 AM - End of day wrap-ups (
/beer) at 5:30 PM - Stale PR reminders every few hours
- Custom workflows on any schedule
Quick Start
Enable the Scheduler
The scheduler is disabled by default. Enable it in config.json:
{
"schedules": {
"enabled": true,
"timezone": "Europe/Dublin"
}
}
Add a Scheduled Job
Use the cron_add tool:
cron_add("morning_coffee", "coffee", cron="30 8 * * 1-5", notify="slack,desktop")
Or edit config.json directly:
{
"schedules": {
"jobs": [
{
"name": "morning_coffee",
"skill": "coffee",
"cron": "30 8 * * 1-5",
"notify": ["slack", "desktop"],
"enabled": true
}
]
}
}
MCP Tools
| Tool | Description |
|---|---|
cron_list |
List all scheduled jobs with next run time |
cron_add |
Add a new scheduled job |
cron_remove |
Remove a scheduled job |
cron_enable |
Enable or disable a job |
cron_run_now |
Manually trigger a job immediately |
cron_status |
Show scheduler status and recent executions |
cron_notifications |
View recent notification history |
Cron Syntax
Standard 5-field cron format:
┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *
Examples
| Expression | Description |
|---|---|
30 8 * * 1-5 |
8:30 AM on weekdays |
0 17 * * 1-5 |
5:00 PM on weekdays |
0 9 * * 1 |
9:00 AM every Monday |
*/30 * * * * |
Every 30 minutes |
0 */4 * * * |
Every 4 hours |
0 0 1 * * |
Midnight on the 1st of each month |
Job Types
Cron Jobs (Time-Based)
Run at specific times:
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.
- 3d ago First seen · 354 lines · 0 tokens per session scan A fbec5152df07
cron is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,101 tokens. 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-31.
Other commands, from other repositories
migrate-nt-to-record
Convert the specified NamedTuple class to use @record from dagstershared.record.
validate_changed_docstrings
Validates Python docstrings in all uncommitted changed files using Sphinx parsing.
resume-work
Resume the current work session by loading active context from localdocs/.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.