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.
curl -O https://raw.githubusercontent.com/chrisreddington/turn-based-game-mcp/main/.github/instructions/ui-components.instructions.mdgit clone --depth 1 https://github.com/chrisreddington/turn-based-game-mcpWrote 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/instructions/chrisreddington/turn-based-game-mcp/ui-components)<a href="https://agentmods.dev/instructions/chrisreddington/turn-based-game-mcp/ui-components"><img src="https://agentmods.dev/badge/instructions/chrisreddington/turn-based-game-mcp/ui-components/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/instructions/chrisreddington/turn-based-game-mcp/ui-components"><img src="https://agentmods.dev/badge/instructions/chrisreddington/turn-based-game-mcp/ui-components.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.00700 | $0.00700 |
| Opus 5.5 | $0.00280 | $0.00280 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
turn-based-game-mcp ui-components.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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Components
Purpose
Patterns for React components in the web package. Covers component structure, styling with TailwindCSS, accessibility, and animations.
Component Structure
- Use TypeScript with proper interface definitions
- Include JSDoc comments for component purpose and complex props
- Use
'use client'directive for interactive components - Export interfaces separately from components
Styling Patterns
- Use TailwindCSS utility classes consistently
- Follow the established design system:
- Gradients:
from-blue-500 to-indigo-600for primary actions - Glass morphism:
bg-white/60 dark:bg-slate-800/60 backdrop-blur-sm - Rounded corners:
rounded-xlfor cards,rounded-lgfor smaller elements - Shadows:
shadow-lg hover:shadow-xlfor interactive elements - Transitions:
transition-all duration-200for smooth interactions
- Gradients:
Component Categories
UI Components (web/src/components/ui/)
- Reusable, generic components (LoadingSpinner, ErrorDisplay, GameControls)
- No game-specific logic
- Highly configurable through props
- Include size variants and theming support
Game Components (web/src/components/games/)
- Game-specific components (TicTacToeBoard, GameInfoPanel)
- Handle game state and user interactions
- Use shared UI components where possible
Shared Components (web/src/components/shared/)
- Components used across multiple games
- MCP integration components
- Cross-game utilities
Props and State Management
- Use controlled components with callback props for state management
- Provide sensible defaults for optional props
- Include loading and disabled states
- Support className prop for style customization
Accessibility Requirements
- Include proper ARIA attributes (
role,aria-label,aria-describedby) - Support keyboard navigation
- Maintain proper heading hierarchy
- Ensure sufficient color contrast
- Use semantic HTML elements
Error Handling
- Handle loading and error states gracefully
- Provide user-friendly error messages
- Include retry mechanisms where appropriate
- Use ErrorBoundary components for critical errors
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 · 114 lines · 700 tokens per session scan A 01c02c97f796
turn-based-game-mcp ui-components.instructions.md is an instructions file published in the GitHub repository chrisreddington/turn-based-game-mcp (31 stars, last pushed 1mo ago), licensed MIT. It adds 700 tokens to every session, about $0.0028 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.