Borrowing it
Nothing to install: this file belongs to Flux-Point-Studios/unreal-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/Flux-Point-Studios/unreal-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Flux-Point-Studios/unreal-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/flux-point-studios/unreal-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/flux-point-studios/unreal-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/flux-point-studios/unreal-mcp/copilot-instructions.svg" alt="Measured on agentmods" 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.00609 | $0.00609 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
unreal-mcp copilot-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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot instructions for Unreal MCP
Big picture
- Dual-process system: TypeScript MCP server in
src/+ Unreal Editor plugin inplugins/McpAutomationBridge/.
Non-obvious constraints (don’t break MCP I/O)
- Keep stdout JSON-only: runtime logs must go through
Logger(seerouteStdoutLogsToStderr()insrc/index.ts). Avoidconsole.login runtime code. .envloading is silenced to protect stdout (seesrc/config.ts).
Key dev commands (from package.json)
- Dev:
npm run dev(ts-node-esm) - Build:
npm run build:core - Plugin sync:
npm run automation:sync
Connection + ports
- The UE plugin listens by default on
127.0.0.1ports8090,8091(seeListenPortsinplugins/.../McpAutomationBridgeSettings.cpp). - The TS bridge connects as a WebSocket client; override with env like
MCP_AUTOMATION_CLIENT_PORTorMCP_AUTOMATION_WS_PORTS(seesrc/automation/bridge.ts). - Offline mode: set
MOCK_UNREAL_CONNECTION=trueto forceUnrealBridge.tryConnect()to succeed.
Tooling conventions (TS)
- Tool schemas live in
src/tools/consolidated-tool-definitions.ts(action enums + input/output schemas). Output schemas are registered at startup insrc/index.tsand validated by AJV insrc/utils/response-validator.ts. - Tool routing is via
toolRegistry.register()insrc/tools/consolidated-tool-handlers.tsand domain logic insrc/tools/handlers/*-handlers.ts. - Always call Unreal through
executeAutomationRequest()(src/tools/handlers/common-handlers.ts) rather than raw WS.
Safety + normalization
- Console commands are safety-filtered by
src/utils/command-validator.ts; don’t bypass it. - UE calls are throttled/retried via
src/utils/unreal-command-queue.ts. - Prefer
/Game/...paths; some layers normalize/Content→/Game(e.g.src/resources/assets.ts,src/tools/assets.ts, and plugin helpers inplugins/.../McpAutomationBridgeHelpers.h).
Adding a new action end-to-end
- TS: extend the tool’s
actionenum + schemas insrc/tools/consolidated-tool-definitions.ts. - TS: route the action in
src/tools/consolidated-tool-handlers.ts(or the appropriatesrc/tools/handlers/*-handlers.ts). - C++: implement the action in an appropriate
plugins/.../*Handlers.cppand register it inUMcpAutomationBridgeSubsystem::InitializeHandlers(). - Tests: add/extend a case in
tests/integration.mjs.
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.
- 8d ago First seen · 35 lines · 609 tokens per session scan A f2a29d10c557
unreal-mcp copilot-instructions.md is an instructions file published in the GitHub repository Flux-Point-Studios/unreal-mcp (8 stars, last pushed 4mo ago), licensed MIT. It adds 609 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.