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/arbazkhan971/godmode/cronnpx skills add arbazkhan971/godmode --skill crongit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/cron)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/cron"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/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.1 | $0.00033 | $0.02690 |
| Opus 5 | $0.00016 | $0.01345 |
| Sonnet 5 | $0.00007 | $0.00538 |
| Haiku 4.5 | $0.00003 | $0.00269 |
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 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron — Scheduled Tasks & Recurring Job Orchestration
Activate When
- User invokes
/godmode:cron - User says "schedule a job", "cron job", "recurring task", "run every hour"
- User says "background scheduler", "periodic task", "timed execution"
- User says "node-cron", "BullMQ repeat", "Celery beat", "Sidekiq-cron", "APScheduler", "Hangfire", "Quartz"
- User needs a task to fire on a schedule (daily reports, cleanup, syncs, heartbeats)
- User asks about cron syntax, timezone handling, or overlap protection
- User needs distributed scheduling across multiple instances
- User needs rate-limited or priority-aware recurring execution
- Godmode orchestrator detects hardcoded
setIntervalorsetTimeoutloops that need conversion to proper scheduled jobs
Workflow
Step 1: Scheduling Requirements Assessment
Evaluate what needs to run, how often, and under what constraints:
SCHEDULING REQUIREMENTS ASSESSMENT:
| Dimension | Value |
| Task type | <cleanup | report | sync | alert |
| | billing | digest | health check> |
| Frequency | <seconds | minutes | hourly | |
Cron Expression Quick Reference
CRON EXPRESSION SYNTAX:
| Field | Values | Special chars |
| Minute | 0-59 | * , - / |
| Hour | 0-23 | * , - / |
| Day of month | 1-31 | * , - / ? L W |
Common patterns:
and 7 = Sunday) — check your library
Scheduler Technology Selection Matrix
SCHEDULER TECHNOLOGY SELECTION:
| Technology | Language | Backend | Distributed| Persistence| Ops cost |
|--|--|--|--|--|--|
| node-cron | Node.js | In-proc | No | None | Minimal |
| | Simple cron | (memory) | (single) | (restart | |
| | schedules | | | loses) | |
| | | | | | |
| BullMQ | Node.js | Redis | Yes | Redis | Low |
...
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 · 314 lines · 33 tokens per session scan A 67b9cdc148c4
cron is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 2,690 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
endpoint-validator
Deterministic API endpoint validation with pass/fail reporting.
api-patterns
REST/GraphQL API design: naming, versioning, pagination, idempotency, OpenAPI. Triggers: API design, REST, GraphQL, OpenAPI, Swagger, idempotency, rate limit.
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
api-baas-neon
Serverless PostgreSQL with branching, autoscaling, and edge-compatible driver.
api-caching-strategies
Application-level caching strategies, HTTP caching, cache invalidation, and stampede prevention.
api-database-postgresql
Direct PostgreSQL access with node-postgres (pg) -- connection pools, parameterized queries, transactions, streaming, LISTEN/NOTIFY, error handling.