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 shibing624/agentica --skill crongit clone --depth 1 https://github.com/shibing624/agenticaWrote 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/shibing624/agentica/cron)<a href="https://agentmods.dev/skills/shibing624/agentica/cron"><img src="https://agentmods.dev/badge/skills/shibing624/agentica/cron.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00306 |
| Opus 5 | $0.00026 | $0.00153 |
| Sonnet 5 | $0.00010 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00031 |
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.
What it actually says
Scheduled jobs
Use the cronjob tool. Do not edit crontab or ~/.agentica/cron/jobs.json by
hand. The tool schema lists the actions; do not invent them.
A job runs in a fresh session with none of this conversation. The prompt must be self-contained: goal, constraints, where things are, what to do when blocked. A prompt that needs a follow-up question will stall unattended.
Jobs only fire on their schedule while the scheduler daemon is on. How the user turns it on depends on the surface:
- Interactive CLI: they type
/cron daemon on. You cannot type slash commands; tell them which one./cronis also their surface for list / add / pause / run. - Gateway and other surfaces:
cron.enabledinconfig.yamlis a deployment-level setting. You cannot toggle it from this conversation; tell the user to ask whoever manages this deployment to enable it.
action='run' executes a job once now so you can show the result before
waiting for the schedule.
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 · 30 lines · 52 tokens per session scan A bba5e1a93c7b
cron is a skill published in the GitHub repository shibing624/agentica (351 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 306 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
automation
Create and manage scheduled and price-triggered automations.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output. Use when: (1) monitoring Claude/Codex sessions running in tmux, (2) sending input to interactive terminal applications, (3) scraping output from long-running processes inside tmux, (4) navigating tmux panes/windows…
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…
meetings
Context for working with the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks, and calendar cache live, what the lifecycle states mean, and how the app's agents are driven. Load when the user asks about a meeting's notes or action items, or when writing/reading files under the meetings…
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
interactive-dashboard
Interactive web dashboards: stock trackers, sector heatmaps, portfolio monitors — served via preview URL.