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/eikanya/unitydemosaic/agents-mdgit clone --depth 1 https://github.com/Eikanya/UnityDemosaicWrote 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/eikanya/unitydemosaic/agents-md)<a href="https://agentmods.dev/instructions/eikanya/unitydemosaic/agents-md"><img src="https://agentmods.dev/badge/instructions/eikanya/unitydemosaic/agents-md.svg" alt="Measured on agentmods" 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 | $0.00860 | $0.00860 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
UnityDemosaic 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 75 lines · 860 tokens per session scan A f23d02164734
UnityDemosaic AGENTS.md is an instructions file published in the GitHub repository Eikanya/UnityDemosaic (41 stars, last pushed 6d ago), with no licence file. It adds 860 tokens to every session, about $0.0043 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
unity-mcp CLAUDE.md
Claude Code instructions for CoplayDev/unity-mcp, covering claude.md, what this project is, architecture, three layers on the python side and transport modes.
mcp-unity AGENTS.md
Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
core CLAUDE.md
Claude Code instructions for ReactUnity/core, covering claude.md, what this repo is, two package universes, pnpm workspace membership and commands.
core AGENTS.md
AGENTS.md instructions for ReactUnity/core, covering release workflow, write changelog files, example, fix button hover state and package references.
unity-cli-loop AGENTS.md
AGENTS.md instructions for hatayama/unity-cli-loop, covering architecture overview, repository map, cli / unity package compatibility, project runner pin and generated skill files.
unity-ui-toolkit-design-system AGENTS.md
Instructions for sinanata/unity-ui-toolkit-design-system, covering agents.md, what this project is, golden rules (do not violate), use the design system in your project and repository layout.