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 roedyrustam/vibes-plug --skill cron-scheduler-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/cron-scheduler-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/cron-scheduler-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/cron-scheduler-expert/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/roedyrustam/vibes-plug/cron-scheduler-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/cron-scheduler-expert.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.03661 |
| Opus 5.5 | $0.00028 | $0.01464 |
| Sonnet 5.5 | $0.00014 | $0.00732 |
| Haiku 4.5 | $0.00007 | $0.00366 |
Grade A, and why
cron-scheduler-expert 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 5d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron & Scheduler Expert (2026 Edition)
English
Orchestration & Integration
- Upstream Triggers & Workflows:
async-queue-temporal-expert,event-driven-architect,js-backend-expert - Cloud & Edge Platforms:
cloud-hosting-expert,cloudflare-workers-expert - Domain Consumer Jobs:
saas-billing,email-notification-expert,data-pipeline-etl-expert - Locking & Observability:
database-orm-expert,data-telemetry-expert,logging-error-tracking-expert - Lifecycle & Governance:
zero-to-prod-orchestrator,session-memory-manager
Description
Production-grade guide for implementing scheduled tasks, cron jobs, and recurring background work in modern web applications. Covers Vercel Cron Jobs, Cloudflare Workers Cron Triggers, Inngest scheduled functions, node-cron, BullMQ repeatable jobs, distributed cron locking (Redis-based), timezone-aware scheduling, and common use cases (cleanup jobs, report generation, health checks, subscription renewals).
Trigger Conditions
Activate this skill when:
- Setting up scheduled/recurring tasks (daily reports, cleanup, health checks).
- Configuring Vercel Cron Jobs or Cloudflare Workers Cron Triggers.
- Implementing subscription renewal checks or billing cycle jobs.
- Building data aggregation or ETL pipelines on a schedule.
- Needing distributed cron locking to prevent duplicate execution.
- Scheduling email digests or notification batches.
Platform Selection Guide
| Platform | Best For | Max Frequency | Invocation Model |
|---|---|---|---|
| Vercel Cron | Vercel-hosted Next.js apps | 1/min (Pro), 1/day (Hobby) | HTTP endpoint trigger |
| Cloudflare Workers Cron | Edge-first apps | 1/min | Worker script trigger |
| Inngest | Complex workflows, fan-out | Any (event-driven) | Serverless function |
| BullMQ Repeatable | Self-hosted, Redis-backed | Any | Worker process |
| node-cron | Simple Node.js servers | Any | In-process |
| Trigger.dev v3 | Durable scheduled tasks | Any | Serverless function |
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.
- 5d ago Changed · -7 lines 2ed2a3b151a3
- 6d ago Changed · +1 lines d3d8fbedc554
- 9d ago Changed · +98 lines a0d726e67cc3
- 18d ago Changed eecf1e47748c
- 23d ago Changed 7f48d4f2f4e2
- 24d ago Changed f3596a5a1798
- 26d ago Changed · -6 lines · +58 tokens per session 6cca1cd9ecef
- 28d ago Changed · +6 lines · -58 tokens per session dce45b1a01ac
- 1mo ago Changed beb79cc2b659
- 1mo ago First seen · 305 lines · 70 tokens per session scan A 77dbaa820f87
cron-scheduler-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (114 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,661 once invoked, about $0.0003 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-30.
Other skills, from other repositories
nodejs-backend-patterns
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
builder
Implementing robust business logic, API integrations, data models, and reproducible AI image-generation code with type safety. Use for production implementation, Gemini image API pipelines, or interactive pair programming.
system-and-data-design
Decide whether the system will hold, and where the data lives: requirements and load first, then back-of-the-envelope numbers, building blocks (cache, queue, load balancer, CDN), and the data layer in depth — storage engines, indexes, replication, partitioning, transactions and consistency, batch vs stream. Use when…
evolutionary-modular-architecture
Guides design and implementation of evolutionary modular-monolith platforms with DDD (strategic + tactical), flat-by-aggregate organization, an Anti-Corruption Layer for vendor independence, a transactional outbox for events, smart resilience (backoff with jitter, circuit breakers, idempotency), and a polished…
langgraph-patterns
Production-grade agentic workflows with LangGraph — graph orchestration, state machines, human-in-the-loop, and advanced control flow. Use when building or debugging a LangGraph app, modeling agent state, or adding checkpoints and human approval steps.