Menu
Install, initialize, repair, or check local HOL Guard security protection for OpenClaw.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/hashgraph-online/hol-guard-plugin --skill hol-guardThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Scan AI agent skills, plugins, MCP servers, and agent tooling for prompt injection, unsafe commands, secret exposure, and supply-chain risks before installing or trusting them.
Use when setting up HOL Guard, protecting local AI harnesses, reviewing Guard approvals or receipts, scanning Codex plugins, skills, MCP servers, marketplace packages, or running plugin-scanner verification before release.
Showing SKILL.md
| name | hol-guard |
| description | Install, initialize, repair, or check local HOL Guard security protection for OpenClaw. |
| version | 1.0.0 |
| homepage | https://hol.org/guard |
| user-invocable | true |
| disable-model-invocation | true |
Use this skill only when the user explicitly asks to install, enable, initialize, repair, or check HOL Guard.
HOL Guard is a separate open-source local runtime package. This ClawHub skill is a discovery and setup surface. The hol-guard CLI remains the security authority and owns OpenClaw integration, policy, approvals, and evidence.
Canonical source: https://github.com/hashgraph-online/hol-guard
Start with read-only checks:
command -v hol-guard
If Guard is installed, run:
hol-guard --version
hol-guard status
Report only what the CLI proves. Installing this skill alone does not mean runtime protection is active.
If the user asked only to check Guard, stop after hol-guard status. Do not install or initialize Guard.
Continue with setup only when the user explicitly asked to install, enable, initialize, or repair Guard.
If hol-guard is missing, explain that the next command changes the user's Python/pipx environment and obtain explicit approval before running it:
pipx install hol-guard
If pipx is unavailable, stop and tell the user that the documented HOL Guard install path requires pipx. Do not silently switch package managers and do not execute a remote bootstrap script as a fallback.
After Guard is available, initialize protection interactively:
hol-guard init
Do not add unattended flags unless the user explicitly requests unattended setup. hol-guard init owns the real OpenClaw integration and avoids maintaining a second enforcement implementation in this skill.
Verify the resulting state:
hol-guard status
If protection is degraded, report the failed layer and let the Guard CLI or core documentation drive repair. Do not manually rewrite OpenClaw configuration from this skill unless the core HOL Guard documentation explicitly requires it.
Guard Cloud is optional. Do not require sign-in, credentials, or cloud connectivity for local OpenClaw protection. Offer cloud connection only if the user asks for synchronized history, shared policy, fleet visibility, or team approvals.
.env files or unrelated credential stores.hol-guard status proving it.