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/commands/solanabr/solana-ai-kit/build-app)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/build-app"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/build-app/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/build-app"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/build-app.svg" alt="Reviewed on agentmods" width="80" 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.02015 |
| Opus 5 | $0.00006 | $0.01007 |
| Sonnet 5 | $0.00003 | $0.00403 |
| Haiku 4.5 | $0.00001 | $0.00201 |
Grade C, and why
build-app scanned grade C with 1 finding 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are building a web client application. Follow these steps:
Related Skills
- frontend-framework-kit.md - React/Next.js patterns
Step 1: Detect Framework
echo "🔍 Detecting web framework..."
# Check for Next.js
if grep -q "\"next\"" package.json 2>/dev/null; then
echo "⚡ Next.js project detected"
FRAMEWORK="nextjs"
# Check for Vite
elif [ -f "vite.config.ts" ] || [ -f "vite.config.js" ]; then
echo "⚡ Vite project detected"
FRAMEWORK="vite"
# Check for Create React App
elif grep -q "react-scripts" package.json 2>/dev/null; then
echo "⚛️ Create React App detected"
FRAMEWORK="cra"
# Generic React/Node
elif [ -f "package.json" ]; then
echo "📦 Node.js project detected"
FRAMEWORK="node"
else
echo "❌ No package.json found"
exit 1
fi
Step 2: Install Dependencies
echo "📦 Installing dependencies..."
# Check for lock files to determine package manager
if [ -f "pnpm-lock.yaml" ]; then
PKG_MANAGER="pnpm"
elif [ -f "yarn.lock" ]; then
PKG_MANAGER="yarn"
elif [ -f "bun.lockb" ]; then
PKG_MANAGER="bun"
else
PKG_MANAGER="npm"
fi
echo "Using package manager: $PKG_MANAGER"
# Install
$PKG_MANAGER install
Step 3: Environment Configuration
echo "🔧 Checking environment configuration..."
# Check for required env files
if [ -f ".env.example" ] && [ ! -f ".env.local" ]; then
echo "⚠️ Missing .env.local - copying from .env.example"
cp .env.example .env.local
echo "📝 Please update .env.local with your values"
fi
# Verify Solana program ID is set
if grep -q "PROGRAM_ID\|NEXT_PUBLIC_PROGRAM_ID" .env.local 2>/dev/null; then
echo "✅ Program ID configured"
else
echo "⚠️ Warning: No PROGRAM_ID found in environment"
echo " Add: NEXT_PUBLIC_PROGRAM_ID=<your-program-id>"
fi
# Verify RPC endpoint
if grep -q "RPC_URL\|NEXT_PUBLIC_RPC" .env.local 2>/dev/null; then
echo "✅ RPC endpoint configured"
else
echo "ℹ️ Using default RPC endpoint"
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.
- 9d ago First seen · 334 lines · 13 tokens per session scan C e4f2f0bd6940
build-app is a command published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 19d ago), licensed MIT. It adds 13 tokens to every session and 2,015 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
design-component
Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements.
design
Full design pipeline for a web or web-app target: brief → tokens → generation → motion → review. Use /design:mobile for iOS/Android instead.
design-page
New page or screen in an existing project. Skips design-system creation — reuses the existing design-system.md tokens.
ui
Convert design files (screenshots, Figma exports, wireframes) into production-ready UI components matching the project's conventions. Reads from ui-designs/ by default. Enforces DRY by detecting existing components to reuse. Generates responsive, accessible, typed components with tests and optional Storybook stories.
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.