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-ai-kit/unity-engineergit clone --depth 1 https://github.com/solanabr/solana-ai-kitWhat 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- unity-engineer — 100% identical, 0 lines differ
- unity-engineer — 98% identical, 2 lines differ
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.
- yesterday First seen · 1,095 lines · 86 tokens per session scan A 3f99b6eb5c90
unity-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 11d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
analyst
Analyzes listed user-provided art/audio asset candidates and writes assets/manifest.json. Read-only on game code.