agentmods.dev

open-mmorpg: Command for Claude Code

.claude/commands/planx.md

planx is a command for Claude Code from developerz-ai/open-mmorpg. It costs 30 tokens per session (1,167 once invoked), scanned A, original, MIT.

A command that writes a self-contained implementation plan into the repository's dated planning folders. The plan records the affected code, files, interfaces, constraints, tests, and separate work areas for another coding agent.

In plain words
What is it for?
Use it before a non-trivial change when you want repository exploration and an actionable plan without implementation or code edits.
Why use it?
It removes the need for the implementer to rediscover the project structure and hidden dependencies before coding. Keeping the plan in multiple focused files also makes large work easier to follow.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

This is developerz-ai/open-mmorpg's own configuration. It tells Claude Code how to work on open-mmorpg itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything open-mmorpg configures →

not rated 12repo +1 6d ago A scan 30 tokens original MIT
View source ↗ developerz-ai/open-mmorpg
Reuse

Borrowing it

Nothing to install: this file belongs to developerz-ai/open-mmorpg. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/developerz-ai/open-mmorpg/main/.claude/commands/planx.md
Clone the repo
git clone --depth 1 https://github.com/developerz-ai/open-mmorpg

Made for: Claude Code.

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

agentmods badge for planx

README.md
[![agentmods](https://agentmods.dev/badge/commands/developerz-ai/open-mmorpg/planx/github.svg)](https://agentmods.dev/commands/developerz-ai/open-mmorpg/planx)
Your own site
<a href="https://agentmods.dev/commands/developerz-ai/open-mmorpg/planx"><img src="https://agentmods.dev/badge/commands/developerz-ai/open-mmorpg/planx/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.

agentmods 80×15 button for planx

Your own site · 80×15
<a href="https://agentmods.dev/commands/developerz-ai/open-mmorpg/planx"><img src="https://agentmods.dev/badge/commands/developerz-ai/open-mmorpg/planx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00030 $0.01167
Opus 5.5 $0.00012 $0.00467
Sonnet 5.5 $0.00006 $0.00233
Haiku 4.5 $0.00003 $0.00117

Measured 15d ago against content hash 3d381cf725f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

planx 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 15d 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/commands/planx.md · 82 lines

How it starts

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

/planx

Produce a concise plan another AI can execute with zero extra context. Plan only — no implementation, no code execution, no edits outside the plan dir.

Goal

$ARGUMENTS

Steps

  1. Resolve path. Run date +%Y, date +%m, date +%d. Dir = docs/plans/<YYYY>/<MM>/<DD>/. Glob docs/plans/<YYYY>/<MM>/<DD>/1* → next number = highest existing 1NN-* + 1, else 101. Slug = kebab-case title, max 5 words. Final plan dir: docs/plans/<YYYY>/<MM>/<DD>/<1NN>-<slug>/.

  2. Explore. Task (subagent_type=Explore, thoroughness="very thorough"): existing patterns and files to touch (file:line); which crates/*, modules/*, apps/*, packages/* or content/* are affected; wire types in crates/protocol; the ownership path through crates/persistence; purity constraints on ecs-core / content-schema / sim; tests beside the code; gotchas. Prefer codegraph_explore for structural lookups when .codegraph/ exists. Skip only for trivial asks.

  3. Write the plan as multiple files — never one big plan.md. Always an overview.md index plus one <NN>-<aspect>.md per separable area (e.g. 01-protocol.md, 02-sim.md, 03-persistence.md, 04-content-schema.md, 05-web.md, 06-tests.md).

    overview.md — Goal (1–2 sentences, what + why); Context (stack facts: Rust + tokio, Bevy client, YugabyteDB durable / Dragonfly ephemeral, Bun + SolidJS operator web — only what's relevant) + reference patterns as file:line; Plan files in execution order with a one-line summary each; Done when (verifiable acceptance criteria); Risks / open questions.

    Each <NN>-<aspect>.md — a header line pointing back at overview.md and naming its dependency; Files to change (path:line — what, why); Steps (ordered, concrete, referencing file:line / Type::method rather than restating them); Tests (what to add/run; gate is bin/check — cargo nextest run, cargo clippy --all-targets -D warnings, bun run --filter @omm/web test); Done when.

Read the full file on GitHub · 82 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. 15d ago First seen · 82 lines · 30 tokens per session scan A 3d381cf725f6

Subscribe to this mod's changes

planx is a command published in the GitHub repository developerz-ai/open-mmorpg (12 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 1,167 once invoked, about $0.0001 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-10-02.

PlanningProject managementai-agentsai-nativeaxumbevybunecs
Related

Other commands, from other repositories

maintainer-standup

Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.

coleam00/Archon · 19 tokens

answer

A build round is one archon-ship run on the item. Read how it ended and decide what the queue does next: the item is done, the queue continues it with another round, or a maintainer must decide. The next node performs what you declare and reads it back: it pushes commits the round left unpushed, records your decision…

coleam00/Archon · 0 tokens

route

Decide whether the build queue launches its next run on this item, and write the brief the run starts from. Triage already decided the route; you keep it thin. The next node performs what you declare: it launches archon-ship with your brief, or raises your attention item. You write nothing to the tracker, the…

coleam00/Archon · 0 tokens

decide

Finished runs recorded discoveries: defects and gaps they proved outside their own change. Decide what becomes of each one, once. You judge and author; the next node performs exactly the writes you declare and nothing else. You write nothing to the tracker, the repository or the state store yourself, and the checkout…

coleam00/Archon · 0 tokens

give-up

The queue has run several rounds on this item since its scope last changed, and the last one ended wanting another. Decide whether another round is likely to finish the work, or whether a maintainer should answer the scope question first. The next node records your decision and raises your attention item. You write…

coleam00/Archon · 0 tokens

agent

This file defines the agent command within the simple flow.

fabriqaai/specs.md · 0 tokens