Borrowing it
Nothing to install: this file belongs to solanabr/solana-glossary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solanabr/solana-glossary/main/.claude/commands/build-unity.mdgit clone --depth 1 https://github.com/solanabr/solana-glossaryWrote 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-glossary/build-unity)<a href="https://agentmods.dev/commands/solanabr/solana-glossary/build-unity"><img src="https://agentmods.dev/badge/commands/solanabr/solana-glossary/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.1 | $0.00013 | $0.02181 |
| Opus 5 | $0.00006 | $0.01091 |
| 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 8d 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 build-unity — 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 — 378 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
- unity.md - Unity SDK patterns
- playsolana.md - PlaySolana/PSG1 specifics
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.
- 8d ago First seen · 378 lines · 13 tokens per session scan A eeb9c06a5355
build-unity is a command published in the GitHub repository solanabr/solana-glossary (18 stars, last pushed 28d ago), licensed MIT. It adds 13 tokens to every session and 2,181 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to build-unity, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
d2r-build
Build a D2R character safely — backup, build, scan, verify cycle.
d2r-lookup
Look up D2R game data — items, stats, skills, runewords from extracted game files.
add-tool
Build a new UEFN Toolbelt tool named "$ARGUMENTS". Follow the tool-developer agent workflow exactly.
publish-check
Run a full pre-publish audit. Check everything before the user submits their island to Fortnite.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.