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 humanerd-drew/opencode-drewgent --skill cron-jobs-stalledgit clone --depth 1 https://github.com/humanerd-drew/opencode-drewgentWrote 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/humanerd-drew/opencode-drewgent/cron-jobs-stalled)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/cron-jobs-stalled"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/cron-jobs-stalled/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/humanerd-drew/opencode-drewgent/cron-jobs-stalled"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/cron-jobs-stalled.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.00045 | $0.13747 |
| Opus 5 | $0.00023 | $0.06874 |
| Sonnet 5 | $0.00009 | $0.02749 |
| Haiku 4.5 | $0.00005 | $0.01375 |
Grade A, and why
cron-jobs-stalled 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 10d 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 — 652 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron Jobs Stalled — Diagnostic & Recovery
When user reports "X cron not running" or "X job stopped" or jobs.json shows enabled jobs with no recent execution, this skill diagnoses and recovers.
Triggers:
- "X cron stopped", "X job not running for N days"
~/.{{AGENT_NAME_LOWER}}/cron/jobs.jsonenabled jobs withlast_run_at> 1 day old- All enabled jobs may have
next_run_at: null ~/.{{AGENT_NAME_LOWER}}/cron/output/{job_id}/has no recent files- Output files exist but contain junk (empty body, trivial title)
Step 1: Read jobs.json directly (filesystem truth)
python3 -c "import json; d=json.load(open('$HOME/.{{AGENT_NAME_LOWER}}/cron/jobs.json')); [print(f'{j.get(\"name\",\"?\"):30} enabled={j.get(\"enabled\")} last={str(j.get(\"last_run_at\",\"\"))[:19]} next={str(j.get(\"next_run_at\",\"\"))[:19] or \"NULL\"} status={j.get(\"last_status\",\"\")}') for j in d.get('jobs',[])]"
ls -lt ~/.{{AGENT_NAME_LOWER}}/cron/output/*/ 2>/dev/null | head -30
Don't trust last_status=ok — it's a stale marker. next_run_at is the source of truth for whether the scheduler will run the job.
Output dir name = job_id (12-char hex), NOT job name. cron/output/{job_id}/ directory names are auto-generated from jobs.json id field. To find the dir for a job, read its id from jobs.json, don't guess from the name. (e.g. kanban-dispatcher-integrations has id cb909be06e0e → dir is cron/output/cb909be06e0e/, not cron/output/integrations-board-dispatcher/.)
Step 2: Classify the failure
Five distinct patterns. Diagnose carefully — fix is different for each.
Pattern A: next_run_at: null for recurring jobs (scheduler bug)
Symptoms:
- All (or most) enabled jobs have
next_run_at: null last_run_at1-2 days old- Output dir has no recent files
Root cause: cron/jobs.py get_due_jobs() only calls _recoverable_oneshot_run_at() for null next_run_at. Recurring jobs (schedule.kind in {'cron', 'interval'}) get dropped silently.
What ships with it
2 files 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.
- 10d ago First seen · 652 lines · 45 tokens per session scan A ffb05384fcfd
cron-jobs-stalled is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 13,747 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.