Skip to main content

Install & Setup

Two ways to use Agentic-Z. Pick one, don't run both side-by-side (every skill loads twice and clutters your slash menu).

Option A — Install as a Claude Code plugin (recommended)​

Inside any Claude Code session, run:

/plugin marketplace add DayZ-n-Chill/Agentic-Z
/plugin install agentic-z@dayz-n-chill

Skills appear with the agentic-z: prefix (/agentic-z:dayz-build-pbo). The dayz-rag MCP server registers automatically.

That's it for install. Then in your DayZ mod project:

/dayz-init

The wizard takes care of the rest: env check, scaffold (or import) your mod, junction P:\<ModName>\, optionally stage a test server and build a PBO and launch the diag client.

Use this option if you have an existing project (or empty repo) and want to add Agentic-Z to it without forking. The plugin works in any directory.

Option B — Clone the template (for contributors / power users)​

Use this if you want to read or edit the toolkit itself, or you're starting a brand-new mod from scratch and want the repo layout pre-built.

git clone https://github.com/DayZ-n-Chill/Agentic-Z my-mod
cd my-mod
python .claude\skills\sync-skills\sync.py

sync-skills symlinks the repo's .claude/skills/ into Claude Code, Codex, and Gemini home dirs so all three CLIs discover the same slash commands. Inside Claude Code you can also run /sync-skills as the slash equivalent.

Skills appear unprefixed (/dayz-build-pbo).

Then, same as Option A:

/dayz-init

Use this option if you want to modify agents/skills locally, contribute back to the template, or run the full multi-CLI setup.

After install — verify your environment​

DayZ modding requires DayZ Tools, DayZ Diag, the P:\ drive, and a few one-time setup pieces. The wizard checks all of these on first run and walks you through what's missing. The full reference list with download links lives on the Prerequisites page.

If you want to run preflight standalone (without the wizard):

/dayz-preflight

Or, when Claude Code isn't running yet (e.g. fresh boot, P:\ not mounted):

scripts\setup\preflight.bat
scripts\setup\workdrive.bat

(These .bat wrappers exist for the cold-start cases where you can't reach the slash commands yet. Daily work goes through /dayz-init and the slash commands.)

Next steps​

  • Meet your agents to start generating code and assets.
  • Read the conventions to keep your mod compatible with the template's L2 rules.
  • Browse the workflow for the underlying skill list (/dayz-init orchestrates these, but you can call them directly when you want surgical control).