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 besoeasy/open-skills --skill debug-cron-tmux-startup-failuregit clone --depth 1 https://github.com/besoeasy/open-skillsWrote 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/besoeasy/open-skills/debug-cron-tmux-startup-failure)<a href="https://agentmods.dev/skills/besoeasy/open-skills/debug-cron-tmux-startup-failure"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/debug-cron-tmux-startup-failure/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/besoeasy/open-skills/debug-cron-tmux-startup-failure"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/debug-cron-tmux-startup-failure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 76 YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
- medium Rogue Agent · line 19 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00095 | $0.01841 |
| Opus 5 | $0.00048 | $0.00920 |
| Sonnet 5 | $0.00019 | $0.00368 |
| Haiku 4.5 | $0.00010 | $0.00184 |
Grade A, and why
debug-cron-tmux-startup-failure 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Silent Cron+tmux Startup Failures
Diagnose why an @reboot cron job that is supposed to relaunch persistent tmux sessions (a bot, a dashboard, a watchdog) leaves nothing running, with no visible error and often no log file at all. The two classic silent killers are a bash-only source used inside tmux pane commands and boot-time logs written to a tmpfs /tmp.
Quick quality checklist
- Reproduce under a cron-like environment (
env -i ... SHELL=/bin/sh) so the pane shell matches cron's, not your interactive shell's - Confirm the pane shell before blaming the code: tmux panes run
$SHELL(dash under cron), NOT the script's shebang - Treat missing boot logs in
/tmpas expected on tmpfs systems; redirect boot logs to persistent storage - Confirm the final fix with a clean run in the exact cron environment, not just your shell
When to use
- A service with an
@rebootcrontab entry is not running after reboot;crontab -llooks correct - The cron daemon log shows the job's
CMDline fired, but the process is gone and there is no output file - tmux sessions are created by a start script but
tmux lsreportsno server runningmoments later - A watchdog or manager that auto-restarts via tmux also fails to bring the service back
Required tools / APIs
- Linux with cron, tmux, and bash/dash (no external APIs)
- Optional:
systemd-tmpfiles-cleanawareness for the/tmpboot-log gotcha
Steps
1. Establish that cron fired and what it ran
Check the cron daemon log for the @reboot job's start and end:
journalctl -b | grep -iE "cron.*dannyg|CMD|session opened|session closed"
# Expect roughly: CRON: (user) CMD (path/to/start.sh) ... then seconds later "session closed"
A session closed only a few seconds after CMD means the script ran to completion (or died fast). Next, look for the job's expected output and log files.
2. Check for output files and tmux state
ls -la /tmp/*.out /tmp/boot_*.log 2>/dev/null # the redirect targets from the crontab/script
tmux ls # "no server running" = server died
pgrep -af "your_service|tmux"
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.
- 7d ago First seen · 129 lines · 95 tokens per session scan A aa7ab713db0f
debug-cron-tmux-startup-failure is a skill published in the GitHub repository besoeasy/open-skills (132 stars, last pushed 7d ago), licensed MIT. It adds 95 tokens to every session and 1,841 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
oracle
Oracle second-model review: bundle prompts/files, debug, refactor, design.
ax-cpp-agent-observability
Use when writing C++ code with axllm for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ax-go-agent-observability
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.