dayz-scope-mod

name	dayz-scope-mod
description	Scope the agent to a single mod under workspace/<ModName>/. Adds deny rules to .claude/settings.local.json that block Edit/Write to OTHER mods' workspace folders, P:\<other>\ junctions, and P:\Mods\@<other>\ deploy dirs, so an agent working on Mod A can't accidentally clobber Mod B. Reads stay broad. Use --clear to lift the scope.

Path note: <skill-dir> in commands below is the absolute path of this skill's folder. When the agent loads this skill the harness exposes the skill's base directory; substitute it before running. Sibling skills are reached via <skill-dir>\..\dayz-X\.

/dayz-scope-mod

Scope the agent to a single DayZ mod. While scoped, the agent can read anywhere but cannot Edit or Write to any other mod's source, P:\ junction, or workshop deploy dir. Designed for sessions where you're iterating on one mod and don't want a wrong-instinct call to land in a sibling mod.

Follow .claude/skills/_shared/dayz-conventions.md.

How to run

:: Scope to a specific mod
python "<skill-dir>\scope.py" <ModName>

:: Show current scope (or "no active scope")
python "<skill-dir>\scope.py" --status

:: Lift the scope
python "<skill-dir>\scope.py" --clear

What it does

1. Validates <ModName> exists at workspace/<ModName>/ (refuses unknown names).
2. Reads .claude/settings.local.json, removes any rules previously added by this skill (idempotent re-run).
3. Enumerates sibling mods under workspace/ (every directory except _server, the active mod, and dotted folders).
4. For each sibling mod, appends deny rules to permissions.deny:
   • Edit(workspace/<other>/**), Write(workspace/<other>/**)
   • Edit(P:\<other>\**), Write(P:\<other>\**)
   • Edit(P:\Mods\@<other>\**), Write(P:\Mods\@<other>\**)
5. Writes back .claude/settings.local.json.
6. Records the active mod and the exact rules that were added in .claude/local-memory/dayz-active-scope.json so --clear can undo precisely what was set.

What it does NOT do

• Not a full sandbox. Repo-wide files (.claude/, scripts/, docs/, root configs) stay writable so the agent can keep editing the template and tooling. Only sibling mods are protected.
• Does not gate Bash. A determined Bash(rm -rf workspace/OtherMod) will still go through. Claude Code's permission patterns can't reliably match arbitrary command lines, so this skill protects the high-frequency accidents (Edit/Write) without pretending to be a security boundary. Use this as a guardrail, not a jail.
• Does not auto-update on new mods. If you add a new mod after scoping, re-run /dayz-scope-mod <ActiveMod> to refresh the deny list with the new sibling.
• Does not gate on /dayz-preflight. This is a meta-skill that operates on settings files, not on P:\ content. Safe to run without preflight passing.

When to run

• At the start of a session focused on a single mod.
• After importing or scaffolding a new mod that you then want to lock into.
• Before delegating work to a subagent that might fan out across the workspace.

Skip when:

• Working across multiple mods in the same session.
• Doing template/infrastructure work (skill edits, agent edits, docs).

Output

DayZ scope: SuperMedKit

[OK]    Mod found: workspace\SuperMedKit
[INFO]  Sibling mods detected: 2 (OtherModA, OtherModB)
[OK]    Added 12 deny rules to .claude\settings.local.json
[OK]    Active scope recorded at .claude\local-memory\dayz-active-scope.json

Reads remain broad. Edit/Write to other mods is blocked.
Run /dayz-scope-mod --clear (or scope.py --clear) to lift.

If only one mod exists:

DayZ scope: SuperMedKit

[OK]    Mod found: workspace\SuperMedKit
[INFO]  No sibling mods to deny. Scope is set, but no rules were needed.

If <ModName> does not exist:

[FAIL]  workspace\NoSuchMod does not exist. Known mods:
          - SuperMedKit
        Scaffold first: /dayz-new-mod NoSuchMod  or  /dayz-import-mod --source <path>

Do not

• Don't edit the deny rules manually. Re-run the skill to get them right and to keep dayz-active-scope.json in sync.
• Don't rely on this for security against malicious agents. It blocks high-frequency accidents only.
• Don't run with --clear and forget to re-scope — every Edit/Write to any mod becomes possible again.