Nm Egregore Install Watchdog

Install the egregore watchdog daemon using the OS-native scheduler. Creates a launchd plist (macOS) or systemd timer (Linux) that checks every 5 minutes if e...

Security Scan

The instructions ask the agent/user to run installer scripts and create user scheduler units, but the skill package contains no installer scripts or install spec — the runtime instructions reference local files that are not present, which is an incoherence worth verifying before installing.

Purpose & Capability

The skill's stated purpose (install a watchdog via launchd/systemd) is plausible for the described installer scripts. However the SKILL.md tells the user to run scripts at plugins/egregore/scripts/install_*.sh even though the skill bundle contains no code files or install spec. That mismatch (instructions referencing local scripts that are not included or remotely fetched) is incoherent and may cause the agent or user to fetch or execute code from external sources unexpectedly.

Instruction Scope

The instructions direct creating user-level scheduler units and logs (expected for an installer), and explicitly instruct running bash scripts. But the SKILL.md does not include the script contents or an explicit, trusted URL to retrieve them; it assumes the scripts exist at a relative path. This gives an agent or user unclear guidance and could lead to fetching and executing remote code without the scripts being audited.

Install Mechanism

There is no install spec (instruction-only), which is low-risk if the instructions are self-contained. Here, however, the lack of included scripts combined with instructions to run local installer scripts is problematic: either the skill author expects a pre-existing repo layout, or the agent will need to obtain the scripts from elsewhere. The install mechanism is therefore under-specified.

Credentials

The skill requests no environment variables, no credentials, and no config paths beyond creating user-level scheduler files and writing logs. The requested access is proportionate to installing a per-user watchdog.

Persistence & Privilege

The skill creates a persistent user-level watchdog (launchd plist or systemd user timer) which is reasonable for its purpose. always is false and it does not request system-wide/root installation in the instructions (it even advises running as current user), so requested persistence is limited and proportionate.

What to consider before installing

Do not run or allow the agent to run installers referenced here until you verify the installer scripts. The SKILL.md refers to plugins/egregore/scripts/install_launchd.sh and install_systemd.sh, but no scripts are bundled. Before installing: - Inspect the exact installer scripts (open the files) from the repository homepage (https://github.com/athola/claude-night-market/tree/master/plugins/egregore). Do not run a remote script without reading it. - Confirm the scripts only create user-level launchd plist or systemd user units and do not perform unexpected actions (network calls to unknown hosts, credential exfiltration, writing to system paths, or running as root). - If you want to proceed, either copy the verified scripts into the expected local path or modify the SKILL.md to include the script contents or a fixed trusted URL (e.g., a GitHub release raw URL). Avoid running scripts piped directly to bash from unknown URLs. - Check the log destinations and ensure they are user-writable locations. For systemd, be aware of enabling linger (loginctl) which affects service behavior. If the author can provide the script contents in the skill bundle or an explicit, audited installation URL, the incoherence will be resolved and the assessment could be revised.

Night Market Skill — ported from claude-night-market/egregore. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Install Watchdog

Overview

Installs a persistent daemon that monitors the egregore process and relaunches it when needed. The daemon uses the OS-native scheduler (launchd on macOS, systemd on Linux) to run a watchdog script every 5 minutes.

The watchdog script checks:

• Whether an egregore session is already running.
• Whether the budget is in cooldown.
• Whether there are active work items in the manifest.

If all conditions are met, it launches a new egregore session.

When To Use

• After initializing an egregore project (egregore init) when you want autonomous relaunching.
• When setting up egregore on a new machine.

When NOT To Use

• On CI/CD runners (use the orchestrator directly).
• When you want manual control over session launches.

Installation Steps

1. Detect the operating system

OS=$(uname -s)

2. Run the appropriate installer

macOS (launchd):

bash plugins/egregore/scripts/install_launchd.sh

This script creates a plist at ~/Library/LaunchAgents/com.egregore.watchdog.plist that runs the watchdog script every 300 seconds (5 minutes).

Linux (systemd):

bash plugins/egregore/scripts/install_systemd.sh

This script creates a systemd timer and service unit at ~/.config/systemd/user/ that fires every 5 minutes.

3. Verify installation

macOS:

launchctl list | grep egregore

Expected output: a line containing com.egregore.watchdog with a PID or - status.

Linux:

systemctl --user status egregore-watchdog.timer

Expected output: active (waiting) status.

4. Confirm to the user

Report the installation result, the schedule interval, and the log file location:

• macOS: ~/.egregore/watchdog.log
• Linux: journalctl --user -u egregore-watchdog

Uninstall Command

To remove the watchdog, run:

Skill(egregore:uninstall-watchdog)

Or invoke the uninstall skill directly via the command /egregore:uninstall-watchdog.

Troubleshooting

• Permission denied on plist: ensure the script runs as the current user, not root.
• systemd user session not available: run loginctl enable-linger $USER to enable user services without an active login session.
• Watchdog not firing: check the log output and verify the scheduler is loaded (launchctl list or systemctl --user list-timers).