solana-glossary: Command for Claude Code

.claude/commands/build-unity.md

build-unity is a command for Claude Code from solanabr/solana-glossary. It costs 13 tokens per session (2,181 once invoked), scanned A, a copy of build-unity, MIT.

A command workflow for building Unity game projects for WebGL, desktop, or Android, including projects that use Solana game-development tools. It checks the project and its relevant packages before building.

In plain words
What is it for?
Building Unity games for browsers, Windows, macOS, or Android, with optional checks for the Solana Unity SDK and PlaySolana SDK.
Why use it?
It reduces setup mistakes by confirming that the folder is a Unity project, showing the Unity version and targets, and checking for expected SDK packages.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is solanabr/solana-glossary's own configuration. It tells Claude Code how to work on solana-glossary itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything solana-glossary configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/solanabr/solana-glossary/main/.claude/commands/build-unity.md
Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-glossary

Made for: Claude Code.

Wrote 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.

agentmods badge for build-unity

README.md
[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-glossary/build-unity.svg)](https://agentmods.dev/commands/solanabr/solana-glossary/build-unity)
Your own site
<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>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,181 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash eeb9c06a5355, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

Origin

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.

.claude/commands/build-unity.md · 378 lines

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:

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

Read the full file on GitHub · 378 lines

Changes

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.

  1. 8d ago First seen · 378 lines · 13 tokens per session scan A eeb9c06a5355

Subscribe to this mod's changes

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.