agents-plugins: Instructions file for Claude Code

AGENTS.md

Project overview

agents-plugins is the CS Modding marketplace (csmodding) of agent plugins for Claude Code and OpenAI Codex CLI.

• plugins/coherent-gameface/: flagship plugin. Drives a running Coherent Gameface UI (Cohtml) over a direct CDP WebSocket; TypeScript MCP server (npm @csmodding/gameface-devtools-mcp) + skills.
• plugins/unity-devtools/: drives a running Unity Mono development build over the Mono Soft Debugger protocol (SDB); C# MCP server + SDB class library.

Both are generic toolkits, developed and verified against Cities: Skylines II as the reference target. Each plugin documents its own architecture and gotchas in its AGENTS.md (with a CLAUDE.md symlink).

Everything a plugin ships MUST live inside its plugins/<name>/ directory: marketplace installs copy only that subtree. New plugins get a sibling directory and an entry in both marketplace files.

Tech stack

• mise-en-place: dev tools, env vars and tasks.
• Bun workspaces: the root package.json carries lint/format tooling (oxfmt.config.ts, oxlint.config.ts), lefthook, and what scripts/ and bench/ import; the gameface mcp/ is the only workspace package, and bun.lock lives at the root.
• .NET 10 SDK: the unity-devtools C# projects, grouped by agents-plugins.slnx at the repo root.

Repository structure

• .claude-plugin/marketplace.json and .agents/plugins/marketplace.json: the Claude Code and Codex CLI marketplace files. Both list every plugin.
• .mcp.json (root): LOCAL DEV ONLY, wiring both MCP servers for sessions in this repo (gameface from its committed bundle, unity from sources via dotnet run). Installed users get each plugin's own .mcp.json; keep them in sync when changing server wiring.
• scripts/: check-plugin-sync.ts (manifest consistency) and check-skill-content.ts (the cs2-modding shipped-prose rules, plus the marker spelling and the baseline lines of the gameface skills), both part of mise check; check-skill-changelog.ts (mise skills:check-changelog, network-dependent, not in CI); research-cite-audit.ts (mise research:cite-audit, the cs2-game-update sweep's cite step, reads a local decompile so not in CI).
• .agents/hooks/check-line-length.ts: PostToolUse hook reporting .ts/.cs lines over 100 characters. Synced verbatim from the scrolls repo, which is why oxlint ignores .agents/hooks and oxfmt all of .agents. Markdown is deliberately out of scope: these docs are agent-facing and unwrapped by design.
• .agents/skills/: repo-only maintenance skills, each symlinked from .claude/skills/ and shipped by no plugin. cs2-game-update is the cs2-modding version sweep: the VOLATILE: markers and the baseline lines are its checklist, and it edits docs/research/ and docs/SOURCES.md, which is why it cannot ship. gameface-update sweeps the gameface plugin after the reference target's engine moved, and keeps the probe catalogue beside it. scan-mcp-failures mines this machine's transcripts for failed gameface and unity calls, and feeds the Hits of docs/ROADMAP.md entries. terra-nil-debuggee launches a release Mono game from this machine's Steam library as a second debuggee for the unity server, the shape of a BepInEx-community report.
• docs/ROADMAP.md: planned facets. docs/solutions/: one file per hard-won problem, linked from where it bites. docs/adr/: numbered decision records.
• docs/authoring/: standing authoring contracts. The ticket template any spec's tickets take, pointed at from docs/agents/cantrips-loop.md's publish-tickets verb; and the cs2-modding reference pipeline's own — one shape doc per reference family and the reference-ticket protocol — disclosed out of the plugin's AGENTS.md because only an authoring pass reaches them. check-skill-content.ts enforces both families' prose-line budgets.
• docs/SOURCES.md: every source the cs2-modding pipeline may read, what each settles, and how to locate it. Other files point at it; keep it pointing at as few as possible.
• bench/: the skill-efficacy benchmark, measuring what the four cs2-* skills are worth to an agent writing mod code against the same model without them. Its README.md holds the invocation contract, the task format, and how a run is resumed, calibrated and promoted; core.ts holds every decision and run.ts is a thin, deliberately untested shell. results.md is the tracked baseline, written only by mise bench:promote from an Opus run, never by hand.
• docs/research/: the cs2-modding pipeline's cited stage, sitting outside plugins/ so none of it ships. Its README.md holds the conventions a research file satisfies; nothing under plugins/ may reference it or SOURCES.md, and check-skill-content.ts fails any shipped link resolving outside the plugin directory, since existence alone passes one that works here and dead-ends for every installed user.