# git-safe demo 1. The isolated fixture supplies a repository with a post-checkout hook and agent-targeted instructions, plus a hostile Git configuration that enables the tracked hook. A raw control clone must execute that hook before the demonstration starts; no user Git configuration is modified. 2. It calls `git_clone_safe` instead of raw `git clone`; the clone lands in a subdirectory with hooks disabled, LFS filters stripped, and size and file counts checked. 3. The result line reports path, file and byte counts, and warnings. 4. The agent reads the repository's README; the content comes back wrapped as untrusted data with a git-specific warning, so the embedded instructions stay data. 5. The final assertion requires the control clone's hook marker to exist and the safe clone's marker to be absent under the same fixture Git configuration. Protagonist: git-safe. Supporting: nu-bang for the proof. Point: clone and read foreign code without letting it execute or speak as the user.