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 instructions/haolange/infinityrenderpipeline/agents-mdgit clone --depth 1 https://github.com/haolange/InfinityRenderPipelineWhat 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.05244 | $0.05244 |
| Opus 5 | $0.02622 | $0.02622 |
| Sonnet 5 | $0.01049 | $0.01049 |
| Haiku 4.5 | $0.00524 | $0.00524 |
Grade A, and why
InfinityRenderPipeline AGENTS.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 3d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InfinityRP Agent Guide
This document defines coding conventions and collaboration rules for com.infinity.render-pipeline (InfinityRP).
Architecture principles
- Entity data belongs to the entity; draw descriptions only reference it. One logical object owns one
TransformId/ bounds. Submesh, material, and pass only addMeshDraw/ template references. - Cache stable templates; regenerate view results.
MeshPassDrawis cacheable. Visibility, LOD, sort order, and compaction are per request/view. - One public Mesh Drawing API for CPU and GPU backends. Callers use
MeshDrawRequest/RGDrawListRef; backends stay internal. - RenderGraph-native lifecycle.
DeclareDrawListrecords only; structural pass culling runs first; only live DrawLists schedule work; cleanup is graph-owned. - No legacy / deprecated compatibility layers. When a path is replaced, delete the old ownership path. Do not keep dual authorities.
Naming
| Kind | Convention | Examples |
|---|---|---|
| Namespace | InfinityTech.<Domain>[.<Sub>][.Editor] |
InfinityTech.Rendering.MeshPipeline |
| Enum | E prefix |
EPassType, EMeshBackendPolicy |
| Geometry / handle struct | F prefix |
FBound, FBufferRef, FPlane |
| RenderGraph type | RG prefix |
RGBuilder, RGDrawListRef |
| Job | *Job suffix |
MeshInstanceCullingJob |
| Private instance field | m_ + PascalCase |
m_RGBuilder |
| Static readonly | s_ prefix |
s_Shader |
| Shader property IDs | ID_ or semantic names on InfinityShaderIDs |
TransformBuffer |
| Shader bindings | SRV_ / UAV_ / CBV_ (HLSL/C#) |
SRV_DepthTexture |
Organization
- Extend
InfinityRenderPipelineonly viapartialfiles underRuntime/RenderPipeline/Pass/. - Pass file pattern:
XxxPassDatastruct + optionalXxxPassUtilityData+ pipeline method. - Prefer
#regionin Editor inspectors; avoid in hot Runtime paths. - One primary type per file unless Pass/Feature grouping clearly benefits.
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.
- 3d ago First seen · 184 lines · 5,244 tokens per session scan A a04129463892
InfinityRenderPipeline AGENTS.md is an instructions file published in the GitHub repository haolange/InfinityRenderPipeline (271 stars, last pushed 17d ago), licensed MPL-2.0. It adds 5,244 tokens to every session, about $0.0262 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-30.
Other instructions, from other repositories
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.