Agentic-Z

An AI Agent Stack for DayZ Modding — clone it, and your repo comes pre-loaded with specialist agents, slash commands, and a local RAG index that turn Claude Code, Codex, or Gemini CLI into a competent DayZ modding co-author.

---

What you get

• A 30-agent mod team: an orchestrator that plans and tracks a whole mod, a Haiku router that picks the handler for a request, team leads, specialists for scripts, configs, models, textures, UI, Figma, maps, server admin, Workbench plugins, saving data, AI, vehicles, weapons, wearables, animation, audio and effects, and physics, and gatekeepers that review, build and test every task in game before you see it.
• 44 slash-command skills (40 in the plugin, plus 4 clone-only template-maintenance skills) that drive DayZ Tools end-to-end — preflight, scaffold, build PBOs, launch a local diag server + client, manage types.xml, scope the agent to a single mod, etc.
• A semantic-search RAG over the vanilla DayZ source (Enforce Script, configs, layouts, materials), exposed through the dayz-rag MCP server to the specialists, reviewer, debugger, architect and layout agents. Embeddings via Voyage AI (voyage-code-3) stored in LanceDB; needs VOYAGE_API_KEY in .env. Skip the build with /dayz-search-download, which pulls the prebuilt index from GitHub releases.
• Three-CLI support out of the box. The same skills and rules files work in Claude Code, Codex CLI, and Gemini CLI. One sync-skills run wires the skills up in all three. The agents, hooks and RAG server are Claude Code only.

---

Quick start

There are two ways to use Agentic-Z. Either way, Claude Code loads the DayZ agents and skills once, through the agentic-z plugin, with the agentic-z: prefix.

Option A — Clone as a template (recommended for starting a new mod project):

git clone  my-dayz-mod
cd my-dayz-mod
python .claude\skills\sync-skills\sync.py

That symlinks the repo’s skills/ and .claude/skills/ into the Codex and Gemini home directories so they discover the same slash commands. Inside Claude Code you can also run /sync-skills instead. Claude Code itself loads the DayZ agents and skills through the agentic-z@dayz-n-chill plugin that the clone’s .claude/settings.json enables, so they appear with the agentic-z: prefix (/agentic-z:dayz-build-pbo). Only the four template-maintenance skills in .claude/skills/ load from the repo itself, unprefixed.

Option B — Install as a Claude Code plugin (for adding the toolkit to an existing project without forking):

/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.

To install a branch other than main, add the marketplace with the branch after a #: /plugin marketplace add https://github.com/DayZ-n-Chill/Agentic-Z.git#develop. Install from GitHub, not from a local clone folder. The installer copies a local folder whole, including the Windows links a test server (.server//) or an imported mod creates, and without Windows Developer Mode that copy fails with EPERM: operation not permitted, symlink. A clone gets its agents and DayZ skills from the plugin too: its .claude/settings.json adds the dayz-n-chill marketplace from GitHub and enables agentic-z@dayz-n-chill.

Then, from your mod project in Claude Code:

/dayz-init

That’s it. The wizard asks what you’re doing (new mod or import), the mod name, which map to test on, and whether to build and launch. It fixes what it can on its own (mounting P:\, the P:\Mods junction) and gives you the fix or a steam:// link for the rest. Every run after the first shows a status hub for the active mod (PBO age, test servers, whether DayZ Diag is running, search status) and runs the next action you pick. To work on another mod, pick “Set up or switch to another mod” in the hub. Its state lives per clone in .claude/local-memory/ (gitignored).

Power users can still call individual skills directly: /dayz-preflight, /dayz-build-pbo, /dayz-launch-test, etc. See the full slash-command list further down.

Full prerequisites, env-var overrides, and troubleshooting: docs/dayz-modding.md.

---

Prerequisites (one-time, per machine)

Search (optional) embeds through Voyage AI’s hosted API (voyage-code-3, code-tuned, 1024-dim) and stores the vectors in LanceDB under ~/.claude/dayz-search-index/, where the dayz-rag MCP server reads them. Install its Python packages once from the repo root with pip install -r .claude\mcp\dayz-rag\requirements.txt -r skills\dayz-search-index\requirements.txt. Add VOYAGE_API_KEY=pa-… to .env at the repo root; queries need it either way. The last full local build with /dayz-search-index (August 2026, before windowing) embedded about 52,000 chunks and about 66M tokens; the current indexer makes about 62,000 chunks, and its local estimate of about 96M tokens runs high, so check Voyage’s pricing first. To skip the build, /dayz-search-download installs the prebuilt index from GitHub releases with no embedding cost.

---

Architecture — three tiers

L3 files reference L2 in one line. The more specific tier wins ties. Corrections you give the team go into the right tier through /dayz-record-correction.

---

Repo layout

/
├── agents/                 # 30 agents: mod team, router, specialists, agent-creator (L3)
├── skills/                 # 40 plugin slash-command skills (L3) + L2 shared conventions
│   ├── _shared/dayz-conventions.md   # L2 core
│   ├── _shared/conventions/          # L2 topic files (config, assets, scripts, ui, server)
│   └── dayz-*/             # one folder per DayZ skill
├── .claude/
│   ├── skills/             # 4 repo-only skills: agentic-z-update, clean-repo, docs-sync, sync-skills
│   ├── mcp/dayz-rag/       # local RAG MCP server (search_dayz_source, get_dayz_file, ...)
│   ├── agent-memory/       # gitignored, per-agent memory written at runtime
│   ├── local-memory/       # gitignored, per-clone: user/machine notes and /dayz-init state
│   └── settings.local.json # gitignored, per-clone Claude Code settings
├── AGENTS.md / GEMINI.md              # L1 rules for Codex and Gemini (same text as .claude/CLAUDE.md)
├── docs/                   # deep docs (DayZ workflow, model routing)
├── mods/agentic-z-panel/   # Claude Code panel plugin (one-click DayZ buttons)
├── workspace/              # in-progress mods (workspace//)
├── .server/                # local test-server instances (.server//)
└── output/                 # one-shot deliverables

---

DayZ skills (slash commands)

Most skills gate on /dayz-preflight first per L2 conventions. Exceptions, each with its reason, are listed in skills/_shared/dayz-conventions.md: /dayz-stop-test (escape hatch that must work even when the environment is broken), /dayz-scope-mod and /dayz-record-correction (they edit settings or rule files, not DayZ content), /dayz-init (runs preflight inside its own steps), /dayz-workdrive (it mounts the P:\ that preflight checks), /dayz-preflight itself, /dayz-gate (it gates through the scripts it runs), /dayz-search-download (it only downloads a prebuilt index into ~/.claude/ and never reads or writes P:\), /dayz-ask (it only reads vanilla files and checks itself that P:\ is mounted), the skills that only read files and write reports (/dayz-lint, /dayz-balance, /dayz-conflict-check, /dayz-recipe, /dayz-layout-preview, /dayz-upgrade-guard, /dayz-release-pack, /dayz-server-kit, /dayz-health, /dayz-logwatch), /dayz-route and /dayz-statusline.

Front door

Bootstrap (one-time per machine)

Mod scaffolding

Build

Test loop

Gates, routing and status

Editors

Loot economy (types.xml)

Release

Specialist tools (deep)

Search / RAG

Team rules

Cleanup

Claude Code panel (separate plugin)

Template maintenance (clone-only, not in plugin marketplace)

---

The mod team

For a whole mod, start the orchestrator as your main session: claude --agent agentic-z:dayz-orchestrator. It has the architect plan the mod, waits for your yes, then hands tasks to team leads. Every task passes the mod reviewer (and the layout check for UI work) inside its team. After each wave, the orchestrator builds the mod and loads it in game, one test session at a time. When a gate fails, the debugger reads the logs and the task goes back to its worker.

You can still call any specialist below directly for a single task.

DayZ specialist agents

Plus agent-creator for scaffolding new agent definitions.

---

Default rules (L1) at a glance

The full text lives in .claude/CLAUDE.md / AGENTS.md / GEMINI.md.

• Communication — answer first, caveat after. Deliver the underlying answer via available tools; mention any limitation as a one-liner after, never as the lead.
• Tooling — pick the fastest tool for the job. Default Python; cmd/.bat for trivial Windows wrappers; PowerShell only when explicitly asked or genuinely faster; prefer dedicated Read / Edit / Write / Grep / Glob.
• Doc maintenance — plain copies. Edit .claude/CLAUDE.md / AGENTS.md / GEMINI.md together.
• Bootstrap — /sync-skills after cloning. Required so Codex and Gemini see the slash commands.
• Memory — local-memory/ only, never for rules. User/machine-specific notes only; rules go in the repo.
• Subagent routing for DayZ work — route cheaply first. Run /dayz-route on a new DayZ request, and ask the dayz-router agent when it returns "next": "dayz-router". Dispatch the matching dayz-* specialist instead of a generic Superpowers agent. The Figma-to-DayZ pipeline is figma-node-normalizer, then figma-to-dayz-layout, then dayz-layout-validator. Role-to-specialist table in docs/dayz-modding.md.

---

Documentation

• docs/README.md — architecture overview, how to add skills/agents, local-memory rules.
• docs/dayz-modding.md — full DayZ workflow, prerequisites, env vars, troubleshooting.
• docs/model-routing.md — when to use Opus / Sonnet / Haiku and the subagent patterns.
• docs/evals.md: answer tests that score each agent’s answers, so a change can only keep or raise the score.
• docs/prompt-conventions.md — why agent and skill files use caps the way they do (RFC 2119 directives, when to cap, when to stay lowercase).
• The wiki lives in its own private repo, DayZ-n-Chill/Agentic-Z-Wiki (React + MUI, Vite). /docs-sync checks it against this repo when it is cloned next to this one. The old Docusaurus wiki is archived in that repo too, under archive/wiki-docusaurus/.

---

Adding things

A new skill: create skills/my-skill/, add SKILL.md with name/description frontmatter and a “How to run” section, drop the script in, and add it to the skills list in .claude-plugin/plugin.json. Run /sync-skills so Codex and Gemini discover it; to test it in Claude Code before it is published, run /sync-skills --agents claude.

A new agent CLI: append an entry to .claude/skills/sync-skills/agents.json and run /sync-skills. The new home gets links for every skill automatically.

---

Community & contributing

Join us on Discord: discord.gg/dayznchill

Agentic-Z is built by and for the DayZ modding community, and contributions are highly encouraged. Every agent, skill, and convention in this repo started as a real problem someone hit while shipping a mod — the more modders contribute, the sharper the toolkit gets for everyone.

In the Discord you can:

• Learn how to become a contributor. New contributors are walked through the repo layout, the L1/L2/L3 rule structure, and how to land a first PR.
• Propose new agents and skills. If you keep solving the same problem by hand, that’s a skill waiting to be written. Pitch it in Discord and we’ll help shape it.
• Report bugs and rough edges. Path resolution quirks, AddonBuilder errors, agent prompts that miss the mark — all welcome.
• Share what you’ve built. Mods, server setups, custom agents, RAG indexes over your own assets. The toolkit improves fastest when people show what they shipped with it.
• Help refine and enhance the product. Docs improvements, troubleshooting entries, better defaults, new MCP integrations — every contribution compounds.

Whether you’re a seasoned Enforce Script developer, a server admin, a 3D artist, or just learning DayZ modding for the first time, there’s a place for your work here. The goal is a tool that makes DayZ modding accessible and enjoyable for everyone — and that only happens with community input.

---

Security baseline

The shipped configuration is the security baseline. Tighten it for your environment, never loosen it without thinking.

• .claude/settings.json (committed) — narrow Bash allowlist limited to running this repo’s own skills (Bash(python skills/*), Bash(npm list *), etc.) plus an explicit deny list that blocks the dangerous escape hatches: Bash(python -c *), Bash(python -m *), Bash(node -e *), Bash(node -p *), Bash(npm install *), Bash(npx *). Editing this file affects every clone — keep allows narrow and prefer deny rules over removing them.
• .claude/settings.local.json (gitignored, per-clone) — your machine-specific overrides. Never set dangerouslySkipPermissions: true in a long-lived clone; it bypasses every prompt including the deny list. Use /fewer-permission-prompts to build a real allowlist incrementally as you hit prompts.
• agents/*.md — every agent declares an explicit tools: allowlist. Auditor/diagnostic agents cannot Edit/Write: dayz-mod-debugger also has no Bash, and dayz-mod-reviewer gets Bash only to run /dayz-lint. The two run-only gates (dayz-build-checker, dayz-ingame-tester) and dayz-build-engineer get Bash and Skill to run the build and test skills but no Edit/Write. dayz-layout-validator gets Bash and Skill to run the layout syntax check and preview but no Edit/Write; repairs go to figma-to-dayz-layout. dayz-lead can only read and start agents; dayz-orchestrator has the broadest list (including Bash and Agent) because it runs as your main session. Authoring specialists get Read/Write/Edit/Glob/Grep plus the dayz-rag MCP tools; dayz-asset-specialist, dayz-object-builder, dayz-server-admin and dayz-ui-specialist also get Bash and Skill, to run the texture, model, types.xml, imageset and layout preview skills; dayz-script-specialist, dayz-persistence-specialist, dayz-vehicle-specialist, dayz-weapon-specialist and dayz-wearables-specialist also get Bash and Skill, to run /dayz-lint on the mod’s scripts (and /dayz-particles for weapons). dayz-physics-specialist gets Bash and Skill without Edit or Write, to run the model audit. dayz-docs-writer gets Read/Write/Edit/Glob/Grep for the docs plus Bash and Skill, used only to run /dayz-release-pack and /dayz-server-kit and a few read only git status and git log commands. None of the DayZ agents has network tools. The exceptions are agent-creator, which has WebFetch to read the official subagent spec, and figma-node-normalizer, which reads Figma through the Figma MCP server’s read-only tools. Subagents inherit only what’s listed — no implicit full-toolset escalation.

If you fork the repo to publish a downstream variant, run git diff main -- .claude/settings.json agents/ before pushing and convince yourself any widened permissions are intentional.

---

Privacy

Agentic-Z collects no personal data, sends no telemetry, and keeps nothing on any server of its own. Your mods, logs and settings stay on your machine. Two optional features call outside services, and only when you add their API key to .env:

• Voyage AI (VOYAGE_API_KEY): vanilla-source search sends each search question to Voyage AI to turn it into a vector, and /dayz-search-index sends vanilla DayZ source text when you build your own index. See Voyage AI’s privacy policy.
• TypeSafe (TYPESAFE_API_KEY): /dayz-route sends the text of your DayZ request and the names and descriptions of the skills it can pick from, to choose a route. See TypeSafe for its terms.

/dayz-search-download downloads the public prebuilt index from this repo’s GitHub releases and sends nothing about you.

---

License

See LICENSE. Copyright © 2026 DayZ n’ Chill. Source available for non-commercial use only. You may use it free of charge to develop DayZ mods, but you may not sell it, sell services that use it, or make money from anything made with it.