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 commands/solanabr/solana-ai-kit/build-unitygit 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/commands/solanabr/solana-ai-kit/build-unity)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/build-unity"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/build-unity.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.00013 | $0.02178 |
| Opus 5 | $0.00006 | $0.01089 |
| Sonnet 5 | $0.00003 | $0.00436 |
| Haiku 4.5 | $0.00001 | $0.00218 |
Grade A, and why
build-unity 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.
How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are building a Unity project for Solana game development. Follow these steps:
Related Skills
- solana-game SKILL.md - Unity SDK + PlaySolana/PSG1 patterns
Step 1: Identify Project and Target
echo "🎮 Unity Build Process"
echo "====================="
# Check for Unity project
if [ ! -f "ProjectSettings/ProjectVersion.txt" ]; then
echo "❌ Not a Unity project (no ProjectSettings/ProjectVersion.txt)"
exit 1
fi
# Display Unity version
echo "📋 Unity Version:"
cat ProjectSettings/ProjectVersion.txt
# Check build targets
echo ""
echo "📋 Available Build Targets:"
echo " - WebGL (default)"
echo " - StandaloneWindows64"
echo " - StandaloneOSX"
echo " - Android (for PSG1/mobile)"
Step 2: Pre-Build Checks
echo "🔍 Running pre-build checks..."
# Check for Solana.Unity-SDK
if grep -q "com.solana.unity-sdk" Packages/manifest.json 2>/dev/null; then
echo "✅ Solana.Unity-SDK found"
else
echo "⚠️ Solana.Unity-SDK not found in manifest.json"
fi
# Check for PlaySolana SDK (optional)
if grep -q "com.playsolana" Packages/manifest.json 2>/dev/null; then
echo "✅ PlaySolana SDK found - PSG1 target supported"
fi
# Check for compilation errors by refreshing assets
echo "📝 Checking for compilation errors..."
Step 3: Build Commands
WebGL Build (Browser)
echo "🌐 Building WebGL..."
# Standard WebGL build
unity-editor -quit -batchmode -nographics \
-projectPath . \
-buildTarget WebGL \
-executeMethod BuildScript.BuildWebGL \
-logFile build.log
# Check result
if [ $? -eq 0 ]; then
echo "✅ WebGL build successful!"
echo "📁 Output: Build/WebGL/"
else
echo "❌ Build failed. Check build.log for details"
tail -50 build.log
fi
Windows Build (Desktop)
echo "🖥️ Building Windows Standalone..."
unity-editor -quit -batchmode -nographics \
-projectPath . \
-buildTarget Win64 \
-executeMethod BuildScript.BuildWindows \
-logFile build.log
if [ $? -eq 0 ]; then
echo "✅ Windows build successful!"
echo "📁 Output: Build/Windows/"
else
echo "❌ Build failed. Check build.log"
tail -50 build.log
fi
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 · 377 lines · 13 tokens per session scan A a8a535379a0f
build-unity is a command published in the GitHub repository solanabr/solana-ai-kit (99 stars, last pushed 16d ago), licensed MIT. It adds 13 tokens to every session and 2,178 once invoked, about $0.0001 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 commands, from other repositories
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
prompt
Create or optimize prompts using best practices.
db-migrate
You are a database migration expert specializing in zero-downtime deployments, data integrity, and multi-database environments. Create comprehensive migration scripts with rollback strategies, validation checks, and performance optimization.
plan-feature
Production-grade feature planning with dual-AI validation (Claude + Antigravity/Gemini 3 via agy).
perf-budget
Define or review performance budgets, profiling priorities, and target constraints.