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/deploygit 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/deploy)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/deploy"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/deploy.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.02063 |
| Opus 5 | $0.00006 | $0.01032 |
| Sonnet 5 | $0.00003 | $0.00413 |
| Haiku 4.5 | $0.00001 | $0.00206 |
Grade A, and why
deploy 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 4d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are deploying a Solana program. ALWAYS test on devnet before mainnet.
Related Skills
- deployment.md - Full deployment workflow details
- security.md - Pre-deployment security checklist
Step 1: Identify Target Network
echo "🎯 Deployment Target Selection"
echo ""
echo "Choose deployment target:"
echo " 1. devnet (testing - safe, free SOL)"
echo " 2. mainnet (production - REAL SOL, IRREVERSIBLE)"
echo ""
# Check current config
CURRENT_NETWORK=$(solana config get | grep "RPC URL" | awk '{print $3}')
echo "Current network: $CURRENT_NETWORK"
IMPORTANT: If this is a new program, ALWAYS deploy to devnet first.
DEVNET DEPLOYMENT
Step D1: Configure Devnet
echo "🌐 Configuring for devnet..."
solana config set --url devnet
# Verify
solana config get
# Should show: RPC URL: https://api.devnet.solana.com
Step D2: Verify Build
echo "🔨 Building program..."
# Build
if [ -f "Anchor.toml" ]; then
anchor build
else
cargo build-sbf
fi
# Check program exists
ls -lh target/deploy/*.so
Step D3: Fund Wallet
echo "💰 Checking wallet balance..."
solana address
solana balance
# If balance is low, airdrop (devnet only!)
solana airdrop 2
solana balance
Step D4: Deploy to Devnet
echo "🚀 Deploying to devnet..."
if [ -f "Anchor.toml" ]; then
anchor deploy --provider.cluster devnet
else
solana program deploy target/deploy/program.so
fi
# Get program ID
PROGRAM_ID=$(solana address -k target/deploy/program-keypair.json)
echo "✅ Program deployed: $PROGRAM_ID"
# Save program ID
echo $PROGRAM_ID > .program-id-devnet
Step D5: Verify Devnet Deployment
echo "🔍 Verifying deployment..."
solana program show $PROGRAM_ID
# Explorer link
echo ""
echo "📡 Explorer: https://explorer.solana.com/address/$PROGRAM_ID?cluster=devnet"
Step D6: Test on Devnet
echo "🧪 Running devnet tests..."
if [ -f "Anchor.toml" ]; then
anchor test --skip-build --skip-deploy
fi
# Or run custom integration tests
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.
- 4d ago First seen · 354 lines · 13 tokens per session scan A c767f95f5e24
deploy is a command published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 2,063 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
dmaic-fit-improvement
Drive a Six Sigma DMAIC (Define / Measure / Analyze / Improve / Control) cycle for a clinic-wide socket-fit improvement programme — produces the project charter, measurement plan, analysis findings, improvement piloting, and control-phase lock-in.
derive-access-deliverables
Define and batch-produce the public-facing deliverables derived from preservation masters — access copies, IIIF tile pyramids, OCR/transcription, and thumbnails — so the digitized collection is usable, not just safely stored.
recap-module
Generate the four-audience recap that closes a module: a learner recap, a manager nudge, a facilitator log, and (when sponsor is Definitive) a sponsor highlight.
map-evidence
Bind each learning objective to the assessment items that evidence it and define the evidence model — the slip and guess parameters that make Bayesian updating possible (ECD evidence model).
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
doctor
DeepInit preflight — tools, scope, resolved config (and whether it's valid), enabled issue families, estimated cost. 0 tokens, no LLM. Offers to install the freshness hooks.