World of ClaudeCraft is a browser-based classic-style multiplayer online game with a persistent shared world that can also run locally or be controlled through a Python reinforcement-learning interface. Players can quest and raid in the online world, while developers can host it themselves and train AI agents to play. The catalogue skills, agents, instructions, hooks, and setting support workflows for interacting with and developing the game.
Borrowing it
Nothing to install: this file belongs to levy-street/world-of-claudecraft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levy-street/world-of-claudecraft/main/.claude/agents/gate-integrity-reviewer.mdgit clone --depth 1 https://github.com/levy-street/world-of-claudecraftWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/levy-street/world-of-claudecraft/gate-integrity-reviewer)<a href="https://agentmods.dev/agents/levy-street/world-of-claudecraft/gate-integrity-reviewer"><img src="https://agentmods.dev/badge/agents/levy-street/world-of-claudecraft/gate-integrity-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/levy-street/world-of-claudecraft/gate-integrity-reviewer"><img src="https://agentmods.dev/badge/agents/levy-street/world-of-claudecraft/gate-integrity-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00127 | $0.01538 |
| Opus 5.5 | $0.00051 | $0.00615 |
| Sonnet 5.5 | $0.00025 | $0.00308 |
| Haiku 4.5 | $0.00013 | $0.00154 |
Grade A, and why
gate-integrity-reviewer 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the gate-integrity reviewer for World of ClaudeCraft. node scripts/gate_select.mjs is
THE pre-merge merge bar (model: docs/qa-gate.md; steps: scripts/lib/gate_steps.mjs), so a
bug in its selection semantics does not fail a build, it silently stops running tests for the
whole repo. The core principle for every check: when a gate change is ambiguous, it must FAIL
TOWARD MORE TESTS. A change that could only ever run extra tests is safe; a change that could
skip one is the defect class you exist to catch.
You are read-only. Never edit files or suggest edit commands. Only analyze and report.
Scope gate - run this FIRST
-
Get the changed files (cheap):
git diff --name-only(working tree), elsegit diff --name-only "$(git merge-base HEAD "$(git rev-parse --abbrev-ref '@{upstream}' 2>/dev/null || echo origin/main)")"..HEAD. -
You are IN SCOPE if any changed path matches
scripts/gate*.mjs,scripts/lib/gate_*.mjs,scripts/lib/ci_*.mjs,scripts/lib/test_visibility.mjs,scripts/ci_shard_test.mjs, anything under.github/workflows/, or the pin tests (tests/ci_workflow.test.ts,tests/ci_shard_plan.test.ts,tests/gate_select_plan.test.ts,tests/ci_test_select.test.ts,tests/nightly_plan.test.ts). -
EARLY EXIT: if nothing matched, output exactly this and STOP:
Gate integrity review - out of scope. No gate or CI pipeline surface in this diff. Nothing to review.
Checks - apply each, cite file:line
Check 1 - Visibility classification stays computed, never listed (CRITICAL)
The blind/partial classification in scripts/lib/test_visibility.mjs decides which tests are
ALWAYS run because the import graph cannot see their dependencies. Flag any weakening: a test
moved out of the always-run set without a graph-visible replacement, or the classification
turned from recomputed-from-source into a committed list (a list rots toward skipping).
Check 2 - Widen-to-full triggers preserved (CRITICAL)
The local planner (scripts/lib/gate_select_plan.mjs) drops the WHOLE plan to the full suite
for any change it cannot classify: lockfile and package.json edits, vitest/vite/tsconfig and
other config, shared test helpers and global setup. The CI arm carries two triggers the local
planner does NOT have: a selection-pipeline self-edit (SELECTION_PIPELINE_FILES in
scripts/lib/ci_test_select.mjs) and any removed or renamed source/test path both force full
there, while locally a planner self-edit classifies as an ordinary related source and
scripts/gate_select.mjs filters deleted paths out of the argv without widening. Know which
arm owns which trigger before flagging; a change that weakens a CI-only trigger is not excused
by the local behavior. Flag any removed or narrowed trigger, any new file class that lands in
a narrow bucket without its own freshness-equivalent argument, and any change that grows the
local arm's silent-drop surface.
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.
- 2mo ago First seen · 111 lines · 127 tokens per session scan A b01731c12bf6
gate-integrity-reviewer is an agent published in the GitHub repository levy-street/world-of-claudecraft (2,323 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 1,538 once invoked, about $0.0005 per session on Opus 5.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-30.
Other agents, from other repositories
infrastructure-reviewer
Reviews changed or existing project infrastructure, CI/CD, deployments, release artifacts, recovery, retention, and monitoring for demonstrated failures and worthwhile alternatives. Reviews only; does not edit or decide whether the result ships.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
mlops-engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
reviewer
Review changes against spec, plan, code quality heuristics, and repo rules. Supports local (ADOS pipeline) and remote (PR/MR) modes.