Borrowing it
Nothing to install: this file belongs to taygunsavas/patina-unity-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/taygunsavas/patina-unity-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/taygunsavas/patina-unity-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/taygunsavas/patina-unity-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/taygunsavas/patina-unity-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/taygunsavas/patina-unity-mcp/copilot-instructions/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/taygunsavas/patina-unity-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/taygunsavas/patina-unity-mcp/copilot-instructions.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.00378 | $0.00378 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
patina-unity-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 10d 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.
What it actually says
GitHub Copilot review instructions for Patina
Use these instructions when reviewing pull requests in this repository.
Review priorities
- Focus on correctness, regressions, upgrade safety, and contributor-facing workflow risk.
- Prioritize comments on Rust server behavior, Unity package install/runtime contracts, host setup changes, release workflow changes, and repository governance.
- Flag changes that break the source-only repository model or the artifact-first distribution model.
What good feedback looks like here
- Call out API compatibility risks in
rust-server/, especially dependency upgrades and transport changes. - Call out Unity package layout mistakes in
unity-package/, especially anything that would break Package Manager import or packaged runtime expectations. - Call out workflow or release changes that would break validation, artifact assembly, or registry publication.
- Call out repository policy gaps for open-source contribution flow, including missing docs updates when contributor behavior changes.
Review boundaries
- Do not nitpick formatting, naming, or minor style issues unless they hide a correctness or maintainability problem.
- Do not ask for speculative refactors unrelated to the pull request.
- Prefer high-signal comments over broad style commentary.
Repository-specific expectations
docs/is local-only planning context and is not part of the GitHub-facing repository surface.- Public contributor guidance lives in tracked files such as
README.md,CONTRIBUTING.md,ROADMAP.md, and.github/*. - Pull requests should stay focused on one concern and include validation notes when behavior changes.
- Treat
validate / lintandvalidate / rustas the baseline required checks for pull requests targetingmain.
High-risk areas
- Changes to
.github/workflows/* - Changes to
rust-server/src/* - Changes to
unity-package/Editor/* - Changes that alter installation, release, or host configuration behavior
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.
- 10d ago First seen · 37 lines · 378 tokens per session scan A 8444ba72f730
patina-unity-mcp copilot-instructions.md is an instructions file published in the GitHub repository taygunsavas/patina-unity-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 378 tokens to every session, about $0.0019 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).
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.
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.