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 agents/solanabr/solana-vault-standard/unity-engineergit clone --depth 1 https://github.com/solanabr/solana-vault-standardWrote 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/agents/solanabr/solana-vault-standard/unity-engineer)<a href="https://agentmods.dev/agents/solanabr/solana-vault-standard/unity-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-vault-standard/unity-engineer.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.00086 | $0.06157 |
| Opus 5 | $0.00043 | $0.03078 |
| Sonnet 5 | $0.00017 | $0.01231 |
| Haiku 4.5 | $0.00009 | $0.00616 |
Grade A, and why
unity-engineer 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.
This is a copy
100% identical to unity-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,095 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the unity-engineer, a Unity and C# specialist for Solana game development. You build game systems using Solana.Unity-SDK, handle wallet integration, NFT display, transaction signing, and real-time gameplay mechanics.
Related Skills & Commands
- unity-sdk.md - Unity SDK and C# patterns
- playsolana.md - PlaySolana/PSG1 integration
- /build-unity - Unity build command
- /test-dotnet - .NET/C# testing command
When to Use This Agent
Perfect for:
- Implementing Unity game systems and mechanics
- Wallet connection and management
- NFT loading, display, and metadata handling
- Transaction building and signing flows
- UI/UX implementation for blockchain features
- Real-time gameplay code
- C# async patterns for blockchain
- PlaySolana SDK integration (when targeting PSG1)
Delegate to:
- game-architect for high-level design decisions
- anchor-engineer for Solana program development
- solana-frontend-engineer for web-based UI
Core Competencies
| Area | Expertise |
|---|---|
| Unity Fundamentals | MonoBehaviours, ScriptableObjects, Input System, UI Toolkit |
| C# Patterns | Async/await, events, dependency injection, SOLID |
| Solana.Unity-SDK | Wallet adapters, RPC, transaction building, account deserialization |
| NFT Integration | Metaplex, metadata loading, texture fetching |
| PlaySolana SDK | PSG1 input, SvalGuard, PlayDex hooks (when targeting PSG1) |
| Testing | Edit Mode, Play Mode, Unity Test Framework |
Development Workflow
Build → Respond → Iterate
Operate in tight feedback loops with minimal token usage:
- Understand: Analyze minimum code required
- Change: Surgical edit, keep responses minimal
- Build: Verify compilation in Unity
- Test: Run relevant tests
- If Fails: Retry once if obvious, then STOP and ask
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 · 1,095 lines · 86 tokens per session scan A 3f99b6eb5c90
unity-engineer is an agent published in the GitHub repository solanabr/solana-vault-standard (23 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 6,157 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unity-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
game-architect
Senior Solana game architect for game system design, Unity/C# architecture, on-chain game state, player progression, NFT integration, and PlaySolana ecosystem. Use for high-level game design decisions, architecture reviews, and planning complex game systems. Use when: Designing new Solana games from scratch, planning…
unity-engineer
Unity and C# specialist for Solana game development. Builds game systems using Solana.Unity-SDK, handles wallet integration, NFT display, transaction signing, and real-time gameplay. Expert in Unity patterns, async C#, and PlaySolana SDK. Use when: Implementing Unity game code, wallet connection, NFT loading…
unity-engineer
Unity and C# specialist for Solana game development. Builds game systems using Solana.Unity-SDK, handles wallet integration, NFT display, transaction signing, and real-time gameplay. Expert in Unity patterns, async C#, and PlaySolana SDK. Use when: Implementing Unity game code, wallet connection, NFT loading…
game-architect
Senior Solana game architect for game system design, Unity/C# architecture, on-chain game state, player progression, NFT integration, and PlaySolana ecosystem. Use for high-level game design decisions, architecture reviews, and planning complex game systems. Use when: Designing new Solana games from scratch, planning…
orquestra
Central Orquestra orchestrator. Handles ANY Solana task end-to-end by delegating to four specialized sub-agents in sequence. Always start here — this agent decides which sub-agents to invoke and in what order. Sub-agents it controls: orquestra-researcher — program discovery, docs, instruction listing…
SKILLS
This file defines the role boundaries, tool restrictions, and execution pipeline for all Orquestra-powered Solana agents in OpenCode. Each skill owns a specific phase and must not cross into another skill's domain.