How do I install the Mk:freeze skill?

Run npx skillmds@latest add ngocsangyem/mk-freeze 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 Mk:freeze safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mk:freeze?

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 Mk:freeze free to use?

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

Who published Mk:freeze?

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

Mk:freeze by ngocsangyem — Agent Skill

Name: Mk:freeze
Author: ngocsangyem

Mk:freeze

Session-scoped directory edit restriction. Blocks Edit and Write outside the allowed path for the current session only. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". NOT for blocking destructive shell commands (see mk:careful).

ngocsangyem Updated Sep 17, 2026

File contents

/freeze — Restrict Edits to a Directory

Lock file edits to a specific directory. Any Edit or Write operation targeting a file outside the allowed path will be blocked (not just warned).

mkdir -p .meowkit/telemetry
echo '{"skill":"freeze","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}'  >> .meowkit/telemetry/skill-usage.jsonl 2>/dev/null || true

Setup

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

Question: "Which directory should I restrict edits to? Files outside this path will be blocked from editing."
Text input (not multiple choice) — the user types a path.

Once the user provides a directory path:

Resolve it to an absolute path:

FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)
echo "$FREEZE_DIR"

Ensure trailing slash and save to the freeze state file:

FREEZE_DIR="${FREEZE_DIR%/}/"
STATE_DIR="${CLAUDE_PLUGIN_DATA:-.meowkit/memory}"
mkdir -p "$STATE_DIR"
echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"
echo "Freeze boundary set: $FREEZE_DIR"

Tell the user: "Edits are now restricted to <path>/. Any Edit or Write outside this directory will be blocked. To change the boundary, run /mk:freeze again. Freeze persists for the session — end the session or start a new one to clear it."

How it works

See references/freeze-mechanics.md for technical details on path resolution, symlink handling, state file persistence, and tool scope.

Hooks

PreToolUse on Edit/Write: Blocks writes outside the frozen directory path
Activated by /mk:freeze <path>. Deactivated when session ends.
Bash commands are NOT restricted — freeze only guards Edit and Write tools

Gotchas

Symlinked files bypass freeze check: Edit tool resolves symlinks, writing outside frozen directory → Check resolved path, not just the stated path
Test files in frozen directory can't update fixtures: Freeze prevents fixture updates needed for new test cases → Use --exclude pattern for test fixtures within frozen scope

---name: mk-freezedescription: Session-scoped directory edit restriction. Blocks Edit and Write outside the allowed path for the current session only. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". NOT for blocking destructive shell commands (see mk:careful).---# /freeze — Restrict Edits to a DirectoryLock file edits to a specific directory. Any Edit or Write operation targetinga file outside the allowed path will be **blocked** (not just warned).```bashmkdir -p .meowkit/telemetryecho '{"skill":"freeze","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}' >> .meowkit/telemetry/skill-usage.jsonl 2>/dev/null || true```## SetupAsk the user which directory to restrict edits to. Use AskUserQuestion:- Question: "Which directory should I restrict edits to? Files outside this path will be blocked from editing."- Text input (not multiple choice) — the user types a path.Once the user provides a directory path:1. Resolve it to an absolute path:```bashFREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)echo "$FREEZE_DIR"```2. Ensure trailing slash and save to the freeze state file:```bashFREEZE_DIR="${FREEZE_DIR%/}/"STATE_DIR="${CLAUDE_PLUGIN_DATA:-.meowkit/memory}"mkdir -p "$STATE_DIR"echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"echo "Freeze boundary set: $FREEZE_DIR"```Tell the user: "Edits are now restricted to `<path>/`. Any Edit or Writeoutside this directory will be blocked. To change the boundary, run `/mk:freeze`again. Freeze persists for the session — end the session or start a new one to clear it."## How it worksSee [references/freeze-mechanics.md](references/freeze-mechanics.md) for technical details on path resolution, symlink handling, state file persistence, and tool scope.## Hooks- **PreToolUse on Edit/Write**: Blocks writes outside the frozen directory path- Activated by `/mk:freeze <path>`. Deactivated when session ends.- Bash commands are NOT restricted — freeze only guards Edit and Write tools## Gotchas- **Symlinked files bypass freeze check**: Edit tool resolves symlinks, writing outside frozen directory → Check resolved path, not just the stated path- **Test files in frozen directory can't update fixtures**: Freeze prevents fixture updates needed for new test cases → Use --exclude pattern for test fixtures within frozen scope

Frequently asked questions