A command that takes a software change from an idea through implementation, verification, pull-request creation, and merging.

Use it for feature work, implementation tasks, fixes, and changes that should end in a merged pull request.

It provides one workflow for checking the existing code, building the change, running the repository's checks, and following the pull request until it lands.

How developerz-ai/ai-gaming-agent-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to developerz-ai/ai-gaming-agent-mcp. 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/ai-gaming-agent-mcp/main/.claude/commands/feature.md

Clone the repo

git clone --depth 1 https://github.com/developerz-ai/ai-gaming-agent-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/developerz-ai/ai-gaming-agent-mcp/feature/github.svg)](https://agentmods.dev/commands/developerz-ai/ai-gaming-agent-mcp/feature)

Your own site

<a href="https://agentmods.dev/commands/developerz-ai/ai-gaming-agent-mcp/feature"><img src="https://agentmods.dev/badge/commands/developerz-ai/ai-gaming-agent-mcp/feature/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/developerz-ai/ai-gaming-agent-mcp/feature"><img src="https://agentmods.dev/badge/commands/developerz-ai/ai-gaming-agent-mcp/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 636 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.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.00636
Opus 5.5	$0.00022	$0.00254
Sonnet 5.5	$0.00011	$0.00127
Haiku 4.5	$0.00005	$0.00064

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

Security

Grade A, and why

feature 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/commands/feature.md · 48 lines

How it starts

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

/feature — idea to merged in developerz-ai/ai-gaming-agent-mcp

Workflow command — established by dz-runner setup mode. Correct it in place; setup never overwrites a command that exists.

Done means MERGED. A green local gate is not done, and an open pull request is not done. Report what you verified, never what you assume happened.

Goal

$ARGUMENTS

Steps

Restate the goal in one line. If it names a URL or an issue, read it first.
Distrust the paperwork. Check any plan, status file or design doc against the code and git log before working from it — trackers rot in both directions. Say plainly which claims you falsified, and fix the doc in the same change.
Explore read-only, in parallel, into a ranked worklist of PR-sized batches.
Build primitive-first: one reusable primitive with its first real caller. No abstraction before a consumer.
Prove it. bin/setup after any dependency change, then bin/check, which here is uv run ruff check src tests && uv run pytest tests/ --ignore=tests/integration -v. Red is not a pull request: fix the cause, never silence the gate. Add the failing test first — a green run that never went red proves nothing.
One pull request in flight, start to finish. Open it, watch it to merged, run git fetch, and only then start the next. Each merge rebases the base under the other, and green-when-opened is not green-to-merge.
Re-check the original symptom after the merge, and leave the issues and docs true.

Fan-out rules — restate these to every agent you spawn

One checkout. No git worktrees. Work would land in a directory nobody is looking at, and each tree costs its own install and its own test database. Disjoint file sets are a scheduling problem you can see; isolation is one you cannot.
Exclusive file sets. Two agents never write one file, and a rename or a signature change pulls every caller into the same set.
No git in a spawned agent — no add, commit, branch, stash or push. You own git, and you touch it only once every agent has returned.
Scope each agent to the files it edited. The repo-wide gate is yours, run once, at the end.

Read the full file on GitHub · 48 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.

2d ago First seen · 48 lines · 54 tokens per session scan A 9ddac50e4058

Subscribe to this mod's changes

feature is a command published in the GitHub repository developerz-ai/ai-gaming-agent-mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 636 once invoked, about $0.0002 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-11-04.

Git and workflow

feature next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
featuredeveloperz-ai/ai-gaming-agent-mcp	Command	2	2d ago	MIT	A	54	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	2d ago	none	A	29	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	4d ago	MIT	A	41	Claude Code

ai-gaming-agent-mcp: Command for Claude Code