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 Stijnman/grok-custom-skills --skill cron-schedulergit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/cron-scheduler)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/cron-scheduler"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/cron-scheduler/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/stijnman/grok-custom-skills/cron-scheduler"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/cron-scheduler.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00434 |
| Opus 5.5 | $0.00010 | $0.00174 |
| Sonnet 5.5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
cron-scheduler 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 2mo 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
Cron Scheduler
When to Use
- User says schedule this or task matches this capability
- User says run daily or task matches this capability
- User says cron job or task matches this capability
- User says set timer or task matches this capability
- User says every morning or task matches this capability
Workflow
- Parse the schedule expression (cron, interval, or natural language).
- Present the proposed trigger, task scope, notification channel, and next three run times.
- Obtain explicit user approval before writing or enabling any recurring schedule; otherwise provide an inactive copy-paste configuration only.
- After approval, save only the named configuration and do not enable background execution, outbound notifications, or external actions beyond the approved scope.
- On trigger, execute only the preapproved task. Pause for fresh approval before any consequential external action not explicitly covered by that approval.
References
Read references/scheduling.md when setup, backends, or rubric details are needed.
Integrations
insight-synthesizergoal-verifier
Error Handling
| Failure | Response |
|---|---|
| Invalid cron | Show valid example: 0 9 * * 1-5 (weekdays 9am). |
| No workspace write access | Output schedule as copy-paste block only. |
Gotchas
- Read references/scheduling.md for backend options.
Example
Input: User request matching triggers above. Output: Structured result per workflow with integrations invoked as needed.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 54 lines · 26 tokens per session scan A b84773f809e7
cron-scheduler is a skill published in the GitHub repository Stijnman/grok-custom-skills (14 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 434 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
template-engine
Load, validate, and populate templates consistently across frameworks.
checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position.
runtime-info
Display a comprehensive runtime environment report covering detected provider, available tools, AIWG version, and installed frameworks.
uninstall-plugin
Remove a previously installed Claude Code marketplace plugin and unregister it from the local plugin registry.
update
Update AIWG through its install-aware updater and re-deploy all installed frameworks from the registry.
run
Execute a named script defined in .aiwg/aiwg.config or list all available scripts.