turn-based-game-mcp: Instructions file for GitHub Copilot

.github/instructions/api-routes.instructions.md

turn-based-game-mcp api-routes.instructions.md is an instructions file for GitHub Copilot from chrisreddington/turn-based-game-mcp. It costs 1,055 tokens per session, scanned A, original, MIT.

A set of patterns for building web API endpoints in Next.js, a JavaScript framework for web applications, for a turn-based games platform. It covers route files, request methods, validation, game integration, errors, and security.

In plain words
What is it for?
Use it when adding GET, POST, or DELETE endpoints for game types and game instances, including endpoints designed for MCP clients.
Why use it?
It provides a consistent structure for handling requests and responses and helps prevent invalid input from reaching game logic. It also makes routes easier to find and maintain.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is chrisreddington/turn-based-game-mcp's own configuration. It tells GitHub Copilot how to work on turn-based-game-mcp 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 turn-based-game-mcp configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { getGame, setGame } from '../../../lib/game-storage'.

Reuse

Borrowing it

Nothing to install: this file belongs to chrisreddington/turn-based-game-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/chrisreddington/turn-based-game-mcp/main/.github/instructions/api-routes.instructions.md
Clone the repo
git clone --depth 1 https://github.com/chrisreddington/turn-based-game-mcp

Made for: GitHub Copilot.

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 turn-based-game-mcp api-routes.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/chrisreddington/turn-based-game-mcp/api-routes.svg)](https://agentmods.dev/instructions/chrisreddington/turn-based-game-mcp/api-routes)
Your own site
<a href="https://agentmods.dev/instructions/chrisreddington/turn-based-game-mcp/api-routes"><img src="https://agentmods.dev/badge/instructions/chrisreddington/turn-based-game-mcp/api-routes.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,055 This file is loaded in full into every session.
When invoked 1,055 The same file — it is already loaded in full.
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.01055 $0.01055
Opus 5 $0.00528 $0.00528
Sonnet 5 $0.00211 $0.00211
Haiku 4.5 $0.00105 $0.00105

Measured 8d ago against content hash 34ed49996f15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

turn-based-game-mcp api-routes.instructions.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 8d 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.

.github/instructions/api-routes.instructions.md · 153 lines

How it starts

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

Next.js API Routes

Purpose

Patterns for creating API routes in the web package. Covers request handling, game integration, error handling, and security.

File Structure and Naming

  • Use Next.js 13+ App Router conventions (route.ts)
  • Group related routes by game type: /api/games/[game-type]/
  • Use dynamic routes for game instances: /api/games/[game-type]/[id]/
  • Include MCP-specific sanitized endpoints: /api/games/[game-type]/mcp/

HTTP Method Handlers

Export named functions for each HTTP method:

import { NextRequest, NextResponse } from 'next/server'

export async function GET() {
  // Handle GET requests
}

export async function POST(request: NextRequest) {
  // Handle POST requests with body
}

export async function DELETE(request: NextRequest) {
  // Handle DELETE requests
}

Request/Response Patterns

Request Handling

  • Always use try-catch blocks for error handling
  • Parse request bodies with await request.json()
  • Extract URL parameters from dynamic routes: { params }: { params: Promise<{ id: string }> }
  • Validate required fields and return 400 for missing data

Response Patterns

  • Use NextResponse.json() for all responses
  • Include appropriate HTTP status codes:
    • 200: Success
    • 400: Bad request (validation errors, invalid moves)
    • 404: Resource not found
    • 500: Server errors
  • Return consistent error shapes: { error: 'Error message' }

Game Integration Patterns

Game State Management

  • Create game instances at module level: const ticTacToeGame = new TicTacToeGame()
  • Use shared game storage functions from @turn-based-mcp/shared
  • Always validate moves using game logic before applying
  • Update game history with player moves and timestamps

Move Processing Flow

// 1. Validate game exists
const gameSession = await getGameFromStorage(gameId)
if (!gameSession) {
  return NextResponse.json({ error: 'Game not found' }, { status: 404 })
}

// 2. Validate move
if (!gameInstance.validateMove(gameSession.gameState, move, playerId)) {
  return NextResponse.json({ error: 'Invalid move' }, { status: 400 })
}

// 3. Apply move and update state
let updatedGameState = gameInstance.applyMove(gameSession.gameState, move, playerId)

// 4. Add to history
const playerMove = { playerId, move, timestamp: new Date() }
gameSession.history.push(playerMove)

// 5. Check for game end
const gameResult = gameInstance.checkGameEnd(updatedGameState)
if (gameResult) {
  updatedGameState = { ...updatedGameState, status: 'finished', winner: gameResult.winner }
}

// 6. Save and return
gameSession.gameState = updatedGameState
await saveGameToStorage(gameId, gameSession)
return NextResponse.json(gameSession)

Read the full file on GitHub · 153 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. 8d ago First seen · 153 lines · 1,055 tokens per session scan A 34ed49996f15

Subscribe to this mod's changes

turn-based-game-mcp api-routes.instructions.md is an instructions file published in the GitHub repository chrisreddington/turn-based-game-mcp (31 stars, last pushed today), licensed MIT. It adds 1,055 tokens to every session, about $0.0053 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-30.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens