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/haolange/InfinityRenderPipelineWrote 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/haolange/infinityrenderpipeline/unity-refresh-iterate)<a href="https://agentmods.dev/rules/haolange/infinityrenderpipeline/unity-refresh-iterate"><img src="https://agentmods.dev/badge/rules/haolange/infinityrenderpipeline/unity-refresh-iterate/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/haolange/infinityrenderpipeline/unity-refresh-iterate"><img src="https://agentmods.dev/badge/rules/haolange/infinityrenderpipeline/unity-refresh-iterate.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.00411 | $0.00411 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
unity-refresh-iterate 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
Unity Refresh + Log + Frame Iterate
After any InfinityRP code/shader change, do not wait for the user to compile.
- Confirm the explicitly owned Editor and project path. Never connect to or operate another session. When the source is occupied, use the authorized independent task mirror and Library.
- Refresh that explicit project with Unity CLI or
Tools/RefreshUnityEditor.sh/.ps1, which invoke publicAssetDatabase.Refresh. UI inspection uses Computer Use on the verified owned window. - Wait for compilation/domain reload to finish and verify the candidate DLL loaded. Read new diagnostics from that Editor's actual log (
Application.consoleLogPath); stable logs alone are not acceptance. - Diagnose only new log after the mark. Fix the first real owner/order/lifetime/shader-contract defect.
- Capture the frame with
Tools/CaptureUnityWindow.sh(macOS) orTools/CaptureUnityWindow.ps1(Windows) and inspect the image. Console-clean is not render-correct: a depth-clear regression once held the Console at 0 errors while the Game view rendered nothing. Always capture after touching clears, depth, attachments, pass order, or present. - Forbidden as a "fix":
if (shader == null) returnin execute, dummy textures, disabling a designed path to silence Console, fake history, orcount = 0dispatches. - Unimplemented features must not be recorded. Required producers (Lighting, TAA when that path is active, Display) must fail at record/setup if their contract is broken.
- Repeat refresh → log → frame → first-principles fix until the new log window has no InfinityRP flood and the captured frame is correct. Keep
TODO(UNVERIFIED)on any result that was checked by log only.
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 Changed · +17 tokens per session 0918800ce4a8
- 1mo ago Changed · +14 tokens per session ba6e790533e5
- 1mo ago First seen · 18 lines · 380 tokens per session scan A 029f49363faf
unity-refresh-iterate is a cursor rule published in the GitHub repository haolange/InfinityRenderPipeline (273 stars, last pushed yesterday), licensed MPL-2.0. It adds 411 tokens to every session, about $0.0016 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 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.