safety-guard

Block dangerous commands in production and autonomous workflows using PreToolUse hooks.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zardusai-cyber/zardus_setup --skill safety-guard-zardusai-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safety-guard
Source: https://github.com/zardusai-cyber/zardus_setup/tree/main/ecc/skills/safety-guard
Command: npx skills add https://github.com/zardusai-cyber/zardus_setup --skill safety-guard-zardusai-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent destructive operations from executing on production systems and during autonomous agent workflows, safeguarding critical assets and configurations.

Core Features & Use Cases

  • Careful Mode: intercepts dangerous commands, warns the user, and suggests safer alternatives.
  • Freeze Mode: locks edits to a specific directory tree to prevent unintended changes.
  • Guard Mode: combines protections for maximum safety in autonomous or high-risk scenarios.
  • Implementation notes: uses PreToolUse hooks to block unsafe actions and logs blocked attempts for auditing.

Quick Start

Enable safety-guard in your development environment to intercept destructive commands and enforce directory restrictions.

Frequently Asked Questions about safety-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent destructive shell commands from executing during automated deployments?

You can prevent destructive shell commands during autonomous agent workflows by enabling Guard Mode, which combines execution interception and directory locking to block unsafe operations and log attempts for auditing.

How do I lock down a directory tree to prevent unintended file edits during migrations?

To lock down a directory tree during migrations, enable Freeze Mode, which actively intercepts and restricts edits to a specific directory tree, preventing unintended changes to critical assets and configurations.

What is the best way to enforce development security and execution control for autonomous agents?

The best way to enforce development security for autonomous agents is to apply protection modes like Guard Mode, which combines execution control and directory locking to safeguard critical assets from destructive operations.

Can I configure execution control rules per-project for sensitive operations?

Yes, you can configure execution control rules per-project or per-session, applying protection across sensitive tasks such as migrations, deployments, and edits to critical directories to intercept dangerous commands.

Does Careful Mode suggest safer alternatives when intercepting dangerous commands?

Yes, Careful Mode intercepts dangerous commands, warns the user, and suggests safer alternatives while logging the blocked actions, providing an execution control layer for sensitive development security tasks.

When should I not use autonomous execution control for production systems?

You should avoid using autonomous execution control without proper configuration when performing sensitive operations, as unconfigured execution may block necessary commands or fail to log destructive operations for auditing properly.