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/furkantokkan/agent-foundryWrote 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/commands/furkantokkan/agent-foundry/unity-dev)<a href="https://agentmods.dev/commands/furkantokkan/agent-foundry/unity-dev"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/unity-dev/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/commands/furkantokkan/agent-foundry/unity-dev"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/unity-dev.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.00020 | $0.00274 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
unity-dev 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 5d 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 Game Dev
Use the unity-game-dev Codex skill for this request. Add
clean-oop-architecture only when the task involves architecture, DI, naming,
testability, or refactoring.
Treat the complete block below as one raw input and preserve quoted paths, logs, references, and constraints:
Read repository instructions and run a read-only Unity preflight before any Editor mutation. Preserve the established composition model inside each bounded context. Existing ServiceLocator/container usage may remain there; otherwise use the repository's accepted Onity policy for genuinely new greenfield work. Do not introduce new Zenject/Extenject, VContainer, UniRx, R3, or MessagePipe usage, and do not add Onity or another package without explicit authorization.
Keep MonoBehaviours thin, plain C# logic testable, and naming consistent with
the canonical m_/s_/k_ policy when no narrower convention exists. Declare
allowed paths, forbidden paths, and one writer for every serialized asset.
Verify changed behavior with focused tests and Unity compilation evidence.
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.
- 5d ago First seen · 30 lines · 20 tokens per session scan A ce5e5a3cd25d
unity-dev is a command published in the GitHub repository furkantokkan/agent-foundry (10 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 274 once invoked, about $0.0001 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-09-25.
Other commands, from other repositories
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
godot-runtime-verify
Verify a built Godot 2D or 3D scene at runtime: run the scene (press-play or headless), read the captured debugger output, classify any runtime errors against a Godot-specific taxonomy, and decide a PASS/FAIL runtime gate for the slice's acceptance behavior. The run's real output IS the Layer-1 runtime evidence…
ui-iterate
Iterate on a Compose screen until it passes the structural gate + visual evaluator — renders the stress matrix, grades it in a separate lane, logs findings to the ledger. Caps at 4 iterations then escalates.
verify
On-demand verification — run tests, check acceptance criteria, validate phase completion.
tests
Backfill or expand tests with Grok (preset).