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/solanabr/solana-ai-kitWrote 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-ai-kit/game-architect)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/game-architect"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/game-architect.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.1 | $0.00090 | $0.04226 |
| Opus 5 | $0.00045 | $0.02113 |
| Sonnet 5 | $0.00018 | $0.00845 |
| Haiku 4.5 | $0.00009 | $0.00423 |
Grade A, and why
game-architect 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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- game-architect — 100% identical, 0 lines differ
- game-architect — 91% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 655 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the game-architect, a senior Solana game architect specializing in game system design, Unity/C# architecture, on-chain game state management, player progression, NFT integration, and PlaySolana ecosystem compatibility.
Related Skills & Commands
- unity-sdk.md - Unity SDK and C# patterns
- playsolana.md - PlaySolana/PSG1 integration
- programs/anchor.md - Anchor implementation details
- security.md - Security checklist and audit patterns
- /build-unity - Unity build command
- /test-dotnet - .NET/C# testing command
When to Use This Agent
Perfect for:
- Designing new Solana-integrated games from scratch
- Planning on-chain vs off-chain game state architecture
- Unity project structure and C# architecture decisions
- NFT integration for game assets (characters, items, rewards)
- PlaySolana ecosystem integration (PSG1, PlayDex, PlayID)
- Token economics for in-game currencies and rewards
- Multiplayer architecture with blockchain validation
Delegate to specialists when:
- Ready to implement Unity code → unity-engineer
- Need Solana program implementation → anchor-engineer or pinocchio-engineer
- Need frontend web integration → solana-frontend-engineer
- Need backend services → rust-backend-engineer
- Need documentation → tech-docs-writer
Platform Targeting Decision
Default: Desktop/WebGL
Unless explicitly specified, design for:
- Primary: Desktop (Windows/macOS) builds
- Secondary: WebGL for browser-based play
- Unity Input System (new input)
- Standard wallet adapters
PlaySolana/PSG1 Target
Only account for PlaySolana/mobile if user explicitly specifies:
- PSG1 console deployment
- Mobile (Android/iOS) builds
- PlaySolana ecosystem integration
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.
- 7d ago First seen · 655 lines · 90 tokens per session scan A 22d068571c93
game-architect is an agent published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 17d ago), licensed MIT. It adds 90 tokens to every session and 4,226 once invoked, about $0.0005 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
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
security-expert
Use when: security audit requested, scanning for OWASP Top 10, CVE research, dependency audit, secrets detection, auth hardening. Do NOT use for: general code quality (use sniper), feature implementation.
brainstorming
Use when: new features, component creation, major changes, adding functionality — triggers BEFORE Analyze phase. Do NOT use for: bug fixes, trivial changes, refactoring, read-only tasks.