Index of every page on this site: llms.txt
All skills
garrytan avatar

/guard

@8586794 official
by Garry Tangarrytan/gstack142k stars
20,987
Run it yourself

Full safety mode: destructive command warnings + directory-scoped edits. Use for: full safety mode, guard against mistakes. (gstack)

Use this Skill: https://skilld.dev/gh/garrytan/gstack/guard

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈35 tokens for metadata: the name and description. ≈619 when used: this file.

Description uses 1.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈140 characters, or 1.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs -->

/guard — Full Safety Mode

Activates both destructive command warnings and directory-scoped edit restrictions. This is the combination of /careful + /freeze in a single command.

Dependency note: This skill references hook scripts from the sibling /careful and /freeze skill directories. Both must be installed (they are installed together by the gstack setup script).

GSTACK_STATE_ROOT=$(~/.claude/skills/gstack/bin/gstack-paths --get GSTACK_STATE_ROOT); : "${GSTACK_STATE_ROOT:?gstack-paths failed; reinstall with ./setup or /gstack-upgrade}"
mkdir -p "$GSTACK_STATE_ROOT"/analytics
echo '{"skill":"guard","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}'  >> "$GSTACK_STATE_ROOT"/analytics/skill-usage.jsonl 2>/dev/null || true

Setup

Ask the user which directory to restrict edits to. Use AskUserQuestion:

  • Question: "Guard mode: which directory should edits be restricted to? Destructive command warnings are always on. Files outside the chosen path will be blocked from editing."
  • Text input (not multiple choice) — the user types a path.

Once the user provides a directory path:

Set the user-selected boundary with the shared writer, which resolves a physical absolute path and serializes replacement with investigation cleanup:

bash "$HOME/.claude/skills/gstack/freeze/bin/freeze-state.sh" set "<user-provided-path>"

On helper failure, do not claim the boundary is active. Preserve the state and report recovery; never bypass the shared writer with a direct write or deletion.

Tell the user:

  • "Guard mode active. Two protections are now running:"
  • "1. Destructive command guard — rm -rf, DROP TABLE, force-push, etc. warn before executing (overridable); catastrophic shapes (recursive delete of /, ~ or a system folder, force-push to main or the default branch, wiping a disk) are hard-denied"
  • "2. Edit boundary — file edits restricted to <path>/. Edits outside this directory are blocked."
  • "To remove the persistent edit boundary, run /unfreeze. Ending the session stops its hooks but does not delete that boundary."

What's protected

See /careful for the full list of destructive command patterns and safe exceptions. See /freeze for how edit boundary enforcement works.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alertstoday3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill provides safety protections by intercepting destructive commands and restricting edits, but it contains a potential command injection surface where user-provided directory paths are not sanitized before being passed to shell commands.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: LOW · No issues

Signed by skilld at 8586794. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
What it can do
Runs commands Reads files
version
0.1.0
triggers
[
  "full safety mode",
  "guard against mistakes",
  "maximum safety"
]
All 3 allowed tools
BashReadAskUserQuestion
Other metadata
hooks
{
  "PreToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c \"exec bash \\\"$HOME/.claude/skills/gstack/careful/bin/check-careful.sh\\\"\"",
          "statusMessage": "Checking for destructive commands..."
        }
      ]
    },
    {
      "matcher": "PowerShell",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c \"exec bash \\\"$HOME/.claude/skills/gstack/careful/bin/check-careful.sh\\\"\"",
          "statusMessage": "Checking for destructive commands..."
        }
      ]
    },
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c \"exec bash \\\"$HOME/.claude/skills/gstack/freeze/bin/check-freeze.sh\\\"\"",
          "statusMessage": "Checking freeze boundary..."
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c \"exec bash \\\"$HOME/.claude/skills/gstack/freeze/bin/check-freeze.sh\\\"\"",
          "statusMessage": "Checking freeze boundary..."
        }
      ]
    },
    {
      "matcher": "NotebookEdit",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c \"exec bash \\\"$HOME/.claude/skills/gstack/freeze/bin/check-freeze.sh\\\"\"",
          "statusMessage": "Checking freeze boundary..."
        }
      ]
    }
  ]
}
  • safety
  • guards
  • destructive-commands
  • edit-boundary
  • bash
  • production
  • workflows

README badge

README badge for garrytan/gstack/guard

Activates destructive command warnings (rm -rf, DROP TABLE, force-push) and restricts file edits to a specified directory. Use when working on production systems or live environments where safety is critical.

Generated from the current SKILL.md.

What commands does guard warn about?
Guard warns before destructive commands like rm -rf, DROP TABLE, and force-push. See the /careful skill for the full list of patterns and safe exceptions.
Can I override the destructive command warnings?
Yes. The warnings are advisory; you can proceed after seeing the warning.
Does guard require both /careful and /freeze to be installed?
Yes. Guard combines both skills and will not work if either sibling skill directory is missing.
How do I remove the edit boundary after enabling guard?
Run /unfreeze to remove the directory restriction. Destructive command warnings remain active until you end the session.

Generated from the current SKILL.md. These answers refresh after source changes.