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 javded-itres/Holix --skill holix-crongit clone --depth 1 https://github.com/javded-itres/HolixWrote 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/javded-itres/holix/holix-cron)<a href="https://agentmods.dev/skills/javded-itres/holix/holix-cron"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/holix-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/javded-itres/holix/holix-cron"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/holix-cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00025 | $0.01296 |
| Opus 5 | $0.00013 | $0.00648 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
holix-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 9d 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.
When to use this skill
The user wants a recurring or scheduled task (daily report, hourly check, weekly backup summary, etc.).
Always use Holix built-in cron — jobs stored in the profile and executed by the gateway scheduler with the same agent stack as chat.
Do NOT
- Do not create or edit system
crontab,launchdplists, orsystemdtimers for Holix agent work. - Do not write standalone Python/bash “scheduler” scripts that loop with
sleepunless the user explicitly needs OS-level scheduling outside Holix. - Do not suggest third-party job runners when
holix gatewaycan run the task.
Prerequisites
- Gateway must be running (scheduler lives inside gateway):
holix gateway start(background) orholix gateway start -f(foreground)holix gateway status— verify running
- Jobs are per profile (
--profile/HOLIX_PROFILE).
Storage (read-only for debugging)
- Jobs:
~/.holix/profiles/<profile>/data/cron/jobs.json - Run log:
~/.holix/profiles/<profile>/data/cron/runs.log
Prefer commands below; edit JSON only if the user insists.
How to create a job
Tell the user the slash command (TUI / Telegram) or run CLI yourself if you have shell access.
Slash (chat):
/cron add <schedule> :: <task description>
Examples:
/cron add every day at 9 :: Summarize yesterday's git activity/cron add every 30 minutes :: Check disk space and alert if >90%/cron add 0 9 * * 1-5 :: Morning standup prep from open issues/cron add hourly :: Quick health check of gateway
CLI (terminal):
holix cron add "every day at 9 :: Summarize logs"
holix cron list
holix cron disable <job-id>
holix cron enable <job-id>
holix cron remove <job-id>
Schedule formats
- Natural language (parsed automatically):
every day at 9:00,every 30 minutes,hourly,daily,weekly,weekdays,every 2 hours - 5-field cron (minute hour day month weekday):
0 9 * * *,*/15 * * * *
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.
- 9d ago First seen · 135 lines · 25 tokens per session scan A 2f69015315e1
holix-cron is a skill published in the GitHub repository javded-itres/Holix (14 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,296 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
cron-scheduler
Schedule and manage automated tasks with cron expressions - create recurring jobs, one-time tasks, natural language scheduling, and cross-platform timer management.
subscription-manager
Create and manage scheduled subscription tasks. Use when the user wants to set up recurring reminders, periodic reports, scheduled checks, or any automated tasks that run on a schedule. Supports cron expressions, fixed intervals, and one-time executions.
c-schedule
Smart scheduling — automate recurring Claude tasks with cost control. Deliver results to Telegram, file, or notification. Built into OpenPaw.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
remindme
⏰ simple Telegram reminders for OpenClaw. cron, zero dependencies.
meeting-notes
OwnPilot official general skill for converting rough meeting notes, transcripts, and call summaries into decisions, action items, owners, risks, and follow-ups. Use when the user provides meeting content or asks for notes.