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.
npx agentmods add rules/muammar-yacoob/unity-mcp/unity_service_patterngit clone --depth 1 https://github.com/muammar-yacoob/unity-mcpWhat 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 | $0.00328 | $0.00328 |
| Opus 5 | $0.00164 | $0.00164 |
| Sonnet 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 2d 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.
- 2d 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 9mo ago), licensed MIT. It adds 328 tokens to every session, about $0.0016 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 cursor rules, from other repositories
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).
monobehaviour-lifecycle
Correct usage of MonoBehaviour lifecycle methods.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
cpp
Cursor rule "cpp" from maddevsio/shared_cursor_rules, covering c++ programming guidelines, basic principles, nomenclature, functions and data.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.