gameforge CLAUDE.md

Repository instructions for Gameforge, a project using Nx, a tool for managing multiple related applications and libraries in one workspace. They cover project setup, commands, generators, documentation, and project context.

In plain words
What is it for?
Exploring the workspace, creating projects, running builds and tests, checking Nx options, and following Gameforge development practices.
Why use it?
They guide the agent toward the repository's required commands and checks, reducing incorrect Nx usage and setup mistakes.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/robcost/gameforge/claude-md
Clone the repo
git clone --depth 1 https://github.com/robcost/gameforge
Per session 952 This file is loaded in full into every session.
When invoked 952 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00952 $0.00952
Opus 5 $0.00476 $0.00476
Sonnet 5 $0.00190 $0.00190
Haiku 4.5 $0.00095 $0.00095

Measured 2d ago against content hash 74e456075855, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gameforge CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

General Guidelines for working with Nx

  • For navigating/exploring the workspace, invoke the nx-workspace skill first - it has patterns for querying projects, targets, and dependencies
  • When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through nx (i.e. nx run, nx run-many, nx affected) instead of using the underlying tooling directly
  • Prefix nx commands with the workspace's package manager (e.g., pnpm nx build, npm exec nx test) - avoids using globally installed CLI
  • You have access to the Nx MCP server and its tools, use them to help the user
  • For Nx plugin best practices, check node_modules/@nx/<plugin>/PLUGIN.md. Not all plugins have this file - proceed without it if unavailable.
  • NEVER guess CLI flags - always check nx_docs or --help first when unsure

Scaffolding & Generators

  • For scaffolding tasks (creating apps, libs, project structure, setup), ALWAYS invoke the nx-generate skill FIRST before exploring or calling MCP tools

When to use nx_docs

  • USE for: advanced config options, unfamiliar flags, migration guides, plugin configuration, edge cases
  • DON'T USE for: basic generator syntax (nx g @nx/react:app), standard commands, things you already know
  • The nx-generate skill handles generator discovery internally - don't call nx_docs just to look up generator syntax

GameForge Project Context

GameForge is an AI-powered game creation platform. Circle 1 MVP is a locally-run builder where users chat with an AI agent team (Designer, Developer, QA) to collaboratively build Phaser 2D games with live preview.

Key Documents

  • PRD: docs/product_requirements_document.md
  • Task Tracking: tasks/todo.md
  • Lessons Learned: tasks/lessons.md

Monorepo Structure

  • apps/ — Next.js and Node.js applications (studio frontend, orchestrator backend)
  • packages/ — Shared libraries consumed by apps (shared-types, game-templates)
  • sessions/ — Runtime game project data per session (gitignored)

Read the full file on GitHub · 72 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 72 lines · 952 tokens per session scan A 74e456075855

Subscribe to this mod's changes

gameforge CLAUDE.md is an instructions file published in the GitHub repository robcost/gameforge (2 stars, last pushed 6mo ago), licensed MIT. It adds 952 tokens to every session, about $0.0048 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.