How do I install the Toolguard Daemon Control skill?

Run npx skillmds@latest add dvcrn/toolguard-daemon-control in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Toolguard Daemon Control safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Toolguard Daemon Control?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Toolguard Daemon Control free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Toolguard Daemon Control?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Toolguard Daemon Control by dvcrn — Agent Skill

Name: Toolguard Daemon Control
Rating: 4.2 (5 reviews)
Author: dvcrn

Toolguard Daemon Control

Manage long-running processes as macOS launchd services. Use when asked to start, stop, restart, check status of, or manage background services/daemons. Handles launchd plist creation, service lifecycle, and log access. Use this instead of background exec for any process that should persist beyond the current session.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

toolguard-daemon-control

Manage any executable as a persistent macOS launchd user agent.

Overview

Services are installed as ~/Library/LaunchAgents/ai.toolguard.<name>.plist and run as user-level launch agents. They auto-restart on failure and log to ~/Library/Logs/toolguard/.

Scripts

All scripts are in scripts/ relative to this skill's directory. Run them with bash.

install.sh — Create and start a service

bash scripts/install.sh <service-name> <command> [args...] [--workdir <dir>] [--env KEY=VALUE ...]

service-name: Short identifier (e.g., toolguard-proxy). Used in plist filename and log paths.
command: Absolute path to the executable.
args: Arguments passed to the command.
--workdir <dir>: Working directory for the process (default: $HOME).
--env KEY=VALUE: Environment variables (repeatable).

Example:

bash scripts/install.sh toolguard-proxy /usr/local/go/bin/go run ./cmd/server --config toolguard.dev.yaml --workdir ~/Documents/toolguard

uninstall.sh — Stop and remove a service

bash scripts/uninstall.sh <service-name>

Unloads the service and removes the plist file. Logs are preserved.

status.sh — Check service status

bash scripts/status.sh [service-name]

Without arguments, lists all ai.toolguard.* services. With a name, shows detailed status for that service.

logs.sh — View service logs

bash scripts/logs.sh <service-name> [--follow] [--lines <n>]

Shows stdout and stderr logs. Default: last 50 lines.

list.sh — List all managed services

bash scripts/list.sh

Lists all installed ai.toolguard.* services with their running state.

Notes

Services run as the current user (no sudo required).
Services auto-restart on crash (KeepAlive = true).
To run a Go project, use the compiled binary path or wrap in a shell script — launchd does not support go run directly. Use go build first, then point to the binary.
Log directory: ~/Library/Logs/toolguard/<service-name>/
Plist location: ~/Library/LaunchAgents/ai.toolguard.<service-name>.plist

---name: toolguard-daemon-controldescription: Manage long-running processes as macOS launchd services. Use when asked to start, stop, restart, check status of, or manage background services/daemons. Handles launchd plist creation, service lifecycle, and log access. Use this instead of background exec for any process that should persist beyond the current session.---# toolguard-daemon-controlManage any executable as a persistent macOS launchd user agent.## OverviewServices are installed as `~/Library/LaunchAgents/ai.toolguard.<name>.plist` and run as user-level launch agents. They auto-restart on failure and log to `~/Library/Logs/toolguard/`.## ScriptsAll scripts are in `scripts/` relative to this skill's directory. Run them with `bash`.### install.sh — Create and start a service```bashbash scripts/install.sh <service-name> <command> [args...] [--workdir <dir>] [--env KEY=VALUE ...]```- `service-name`: Short identifier (e.g., `toolguard-proxy`). Used in plist filename and log paths.- `command`: Absolute path to the executable.- `args`: Arguments passed to the command.- `--workdir <dir>`: Working directory for the process (default: `$HOME`).- `--env KEY=VALUE`: Environment variables (repeatable).Example:```bashbash scripts/install.sh toolguard-proxy /usr/local/go/bin/go run ./cmd/server --config toolguard.dev.yaml --workdir ~/Documents/toolguard```### uninstall.sh — Stop and remove a service```bashbash scripts/uninstall.sh <service-name>```Unloads the service and removes the plist file. Logs are preserved.### status.sh — Check service status```bashbash scripts/status.sh [service-name]```Without arguments, lists all `ai.toolguard.*` services. With a name, shows detailed status for that service.### logs.sh — View service logs```bashbash scripts/logs.sh <service-name> [--follow] [--lines <n>]```Shows stdout and stderr logs. Default: last 50 lines.### list.sh — List all managed services```bashbash scripts/list.sh```Lists all installed `ai.toolguard.*` services with their running state.## Notes- Services run as the current user (no sudo required).- Services auto-restart on crash (`KeepAlive = true`).- To run a Go project, use the compiled binary path or wrap in a shell script — launchd does not support `go run` directly. Use `go build` first, then point to the binary.- Log directory: `~/Library/Logs/toolguard/<service-name>/`- Plist location: `~/Library/LaunchAgents/ai.toolguard.<service-name>.plist`

Frequently asked questions