Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/muammar-yacoob/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/rules/muammar-yacoob/unity-mcp/unity_service_pattern)<a href="https://agentmods.dev/rules/muammar-yacoob/unity-mcp/unity_service_pattern"><img src="https://agentmods.dev/badge/rules/muammar-yacoob/unity-mcp/unity_service_pattern/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/rules/muammar-yacoob/unity-mcp/unity_service_pattern"><img src="https://agentmods.dev/badge/rules/muammar-yacoob/unity-mcp/unity_service_pattern.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.00328 | $0.00328 |
| Opus 5.5 | $0.00131 | $0.00131 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
unity_service_pattern 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 1mo 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
- Extend
BaseServicefor all Unity services- Derive new services from
BaseServiceto inherit the sharedposthelper and transport health checks as shown in BaseService.ts.
- Derive new services from
- Keep request wrappers thin
- Map each Unity endpoint to a short method that forwards parameters to
this.post(endpoint, payload)similar to SceneOperationsService.ts to centralise transport behaviour.
- Map each Unity endpoint to a short method that forwards parameters to
- Prefer typed parameter interfaces
- Declare exported interfaces for every method’s payload (e.g.,
LoadSceneParams,EnterPlayModeParams) so consumers and tools share a single source of truth.
- Declare exported interfaces for every method’s payload (e.g.,
- Default optional arguments at call sites
- Provide default empty objects when parameters are optional (
async getConsoleLogs(params: GetConsoleLogsParams = {})) to prevent undefined payloads from reaching Unity.
- Provide default empty objects when parameters are optional (
- Document method purpose in JSDoc
- Include concise JSDoc comments describing Unity-side behaviour for each RPC method to guide downstream agents and maintain parity with existing service files.
export interface RefreshAssetsParams {
silent?: boolean;
}
export class AssetMaintenanceService extends BaseService {
async refresh(params: RefreshAssetsParams = {}) {
return this.post("/asset/refresh", params);
}
}
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.
- 1mo ago First seen · 29 lines · 328 tokens per session scan A 30f685150da1
unity_service_pattern is a cursor rule published in the GitHub repository muammar-yacoob/unity-mcp (4 stars, last pushed 11mo ago), licensed MIT. It adds 328 tokens to every session, about $0.0013 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-31.
Other cursor rules, from other repositories
meta-quest-agentic-tools
Use Meta Quest Agentic Tools for Meta Quest and Horizon OS samples.
narrative-writing
A set of rules for writing and editing video-game narratives, connected to a narrative project. It requires the agent to load the project's writing context and story canon, which is the established set of story facts, before making changes.
meta-quest-agentic-tools
Use Meta Quest Agentic Tools for Meta Quest and Horizon OS samples.
visual-and-observational-rules
Defines the visual aspects of the game and how the player observes the world. This includes map color-coding, screen effects, and the overall simulation style.
00-project-overview
Base project rule — purpose, constraints, and defaults for mcp-5etools.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.