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/jansenanalytics/claudex/cron-dashboardnpx skills add JansenAnalytics/claudex --skill cron-dashboardgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/cron-dashboard)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/cron-dashboard"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/cron-dashboard.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 | $0.00052 | $0.01433 |
| Opus 5 | $0.00026 | $0.00717 |
| Sonnet 5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
cron-dashboard 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron Dashboard
Unified view of all scheduled jobs, systemd services, and Docker containers with health monitoring.
Binary: ~/bin/cron-dash (or node ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/cron-dashboard/scripts/dashboard.cjs)
Quick Reference
cron-dash status # Full dashboard
cron-dash health # Health check (problems only)
cron-dash next 12 # Upcoming runs in next 12 hours
cron-dash errors # Recent errors across all jobs
cron-dash diagnose monitor # Deep diagnosis of a job
cron-dash logs runner 50 # Last 50 lines of a job's log
Commands
status — Full Dashboard
cron-dash status
Shows everything at a glance:
- All cron jobs with schedule, log age, size, error count, health status
- Systemd services (user + system scope) — only our custom ones
- Docker containers with status
- Summary counts
Health statuses:
| Status | Meaning |
|---|---|
| ✅ healthy | Log updated within expected interval, no errors |
| ⚠️ warning | Some errors in recent log lines |
| ❌ error | Many errors (>5) in recent log output |
| ⏰ stale | Log not updated in 2.5× expected interval |
| ❓ unknown | No log file configured or found |
| ◌ disabled | Cron entry is commented out |
health — Problems Only
cron-dash health
Shows only jobs with issues + actionable suggestions for each.
next [hours] — Upcoming Runs
cron-dash next # Next 6 hours (default)
cron-dash next 24 # Next 24 hours
cron-dash next 1 # Next hour
errors [name] — Recent Errors
cron-dash errors # All jobs
cron-dash errors monitor # Filter by name
Scans last 100 lines of each log for error patterns (error, fail, exception, timeout, refused, etc.).
diagnose <name> — Deep Diagnosis
cron-dash diagnose scan
cron-dash diagnose monitor
Full investigation:
- Schedule and command details
- Log analysis (size, freshness, error count, last line)
- Script existence + permissions check
- Binary/dependency check
- Running process check
- Disk space check
- Actionable suggestions
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.
- 4d ago First seen · 198 lines · 52 tokens per session scan A b7878c2f3eee
cron-dashboard is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,433 once invoked, about $0.0003 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
System Healthcheck
Run a lightweight, non-destructive system healthcheck — disk usage, memory, CPU load, process count, hostname — and store a structured snapshot in session memory. Use when the user says "run a healthcheck", "check system health", "how's the server doing", "is everything ok", or asks for a status/diagnostics snapshot…
mpm-doctor
Run diagnostic checks on Claude MPM installation.
dokan
Operate the dokan runtime — run deterministic scripts in Docker over MCP, compose DAG flows, schedule cron, set secrets, return structured results, read logs token-frugally. Use when the user wants to run/deploy a script or job, build a pipeline/flow/DAG of steps, schedule recurring work, provision API keys for a job…
mpm-status
Display Claude MPM system status.
hunting-persistence-on-linux
Hunts for Linux persistence by inspecting cron, systemd units, shell rc files, SSH authorizedkeys, and common autostart locations for attacker-added entries. Activates for requests to hunt Linux persistence, audit cron/systemd for backdoors, or find unauthorized autostart and authorizedkeys entries.
env-doctor
环境诊断技能 - 运行时检测、端口检查、服务健康、一键修复.