crondex

______________ ____ ____/ /__ _ __ / ___/ ___/ __ \/ __ \/ __ / _ \| |/_/ / /__/ / / /_/ / / / / /_/ / __/> < \___/_/ \____/_/ /_/\__,_/\___/_/|_|

Pre-made cron jobs any AI agent can pull, tweak, and schedule.A directory, not a framework.

Works with Claude, Codex, Hermes, OpenClaw, or any plain LLM with shell access.

npx @wonsukchoi/crondex recommend "warn me before my SSL cert expires" npx @wonsukchoi/crondex show ssl-cert-expiry-check npx @wonsukchoi/crondex deploy ssl-cert-expiry-check --var host=example.com

- recommend "<what you want>"— find the closest matching job (zero tokens, no network call, so an agent can check before writing one from scratch). Matching handles plurals, a small catalog-grounded synonym set (e.g. "notify"/"warn"/"remind" all match jobs taggedreminder), and falls back to fuzzy (edit-distance) matching on typos when nothing matches exactly.
- list [--category x] [--tag y]/categories— browse everything
- show <id>— print a job's full YAML
- next <id> [--count n]— print the next N run times for a job's schedule, in its declared timezone (zero tokens, no network call) — sanity-check a schedule before deploying it
- add <id> [--dest path]— copy it into your project to edit
- init <id> [--category x]— scaffold a brand-new job from the template
- update <path> [--dry-run]— re-pull a job you alreadyadded/inited (matched by itsidfield) against the current catalog, print a diff of what changed, and overwrite it in place.--dry-runshows the diff without applying it.
- deploy <id> --target <crontab|github-actions|systemd|docker|k8s-cronjob|terraform|nomad|eventbridge|cloud-scheduler> [--var name=value ...]— turn a job into something that actually runs (crontab line, GitHub Actions workflow, systemd timer, Dockerfile, k8s CronJob, Terraformkubernetes_cron_job_v1resource, or a readyaws/gcloudcommand).--varoverrides a variable's default.hybridjobs deploycommandby default; add--mode promptfor the prompt side.
- deploy --list-installed— show every crondex-managed line in your crontab (the ones left by--install)
- uninstall <id>— remove one of those installed crontab entries
- doctor [--json]— audit installed crontab entries against the catalog: orphaned entries, schedule drift, and version tagging/staleness. Exits1if any issues were found.
- bundle <file.yaml> [--target <target>] [--dry-run] [--out-dir <path>] [--install]— deploy every job in a manifest in one shot (seeBundles)

claude mcp add crondex -- npx -y @wonsukchoi/crondex mcp

{ "mcpServers": { "crondex": { "command": "npx", "args": ["-y", "@wonsukchoi/crondex", "mcp"] } } }

Tools exposed:crondex_recommend,crondex_list,crondex_categories,crondex_show,crondex_next_runs— each returns the same JSON shape as the matching CLI command's--jsonflag.

Pass--allow-deploy(crondex mcp --allow-deploy, or add it to your MCP client's args) to opt into one more tool:crondex_deploy. It takes the same inputs ascrondex deploy(id,target,vars,mode) and returns the generated artifact text — a crontab line, workflow file, systemd unit pair, etc. It's generation-only: it never writes a file, never touches your crontab, and has no other side effect, so the server stays safe to point an agent at even with--allow-deployon. Without the flag,crondex_deployisn't registered at all.

id: dependency-audit version: 1 name: Dependency Vulnerability Audit category: devops schedule: "0 8   1" # standard 5-field cron runner: hybrid # shell | agent-prompt | hybrid command: | # for runner: shell/hybrid ...raw shell audit, zero tokens... prompt: | # for runner: agent-prompt/hybrid ...instructions with {{repo_path}}, LLM synthesizes+prioritizes... script_note: what you lose by using command instead of prompt variables: repo_path: default: "." compatible_agents: [claude, codex, hermes, openclaw, generic]

- shell— runscommandonly. Zero LLM tokens, deterministic.
- agent-prompt— handspromptto an LLM each run. Costs tokens, but can synthesize, prioritize, and draft prose.
- hybrid— ships both, pick per run: script to save tokens, prompt for more judgment.script_noteexplains the tradeoff.

{{placeholders}}resolve fromvariables— override them for your case, then handcommand/promptplusscheduleto whatever scheduler you have (system crontab, a hosted cron, your agent's own scheduling mechanism). This repo defineswhatto run andwhen, not the executor. Full field spec:schema/job.schema.json.

# bundle.yaml jobs: - id: ssl-cert-expiry-check vars: host: example.com port: "443" - id: dependency-audit vars: repo_path: /srv/app - id: cost-alert mode: prompt

crondex bundle bundle.yaml --target crontab --dry-run # preview crondex bundle bundle.yaml --target crontab --install # install every job crondex bundle bundle.yaml --target github-actions --out-dir .github/workflows

crondex/ ├── llms.txt agent-discovery manifest (llms.txt convention) ├── bin/crondex.js thin CLI entry point — parsing/routing lives in lib/cli.js ├── lib/ cli, doctor, bundle, recommend, deploy, diff, and catalog-building logic (unit tested in test/) ├── catalog.json generated index of every job — read this first ├── schema/job.schema.json spec every job file follows ├── jobs/ one YAML per job, grouped by category subdirectory └── scripts/ build-catalog.js, validate-jobs.js, lint-shell.js, check-duplicates.js, smoke-test.js

SeeCONTRIBUTING.md— copytemplates/job.template.yaml(or runcrondex init), fill it in,npm run validate && npm run build-catalog, open a PR. If you're touching JS inbin/,lib/,scripts/, ortest/, runnpm run formatandnpm run lint(Biome) — CI runs the same lint check. SeeROADMAP.mdfor what's prioritized right now and what's deliberately not built yet.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB