A command for deploying a Solana program first to devnet, Solana's free testing network, and then to mainnet, the live network where transactions use real value.

Use it to select and verify the target network, build the program, check the wallet, fund a devnet wallet when needed, and follow the deployment steps.

It adds a network check and build workflow that reduces the chance of sending an untested program to the irreversible production network.

deploy — Command for Claude Code by solanabr/solana-ai-kit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/solanabr/solana-ai-kit

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/deploy/github.svg)](https://agentmods.dev/commands/solanabr/solana-ai-kit/deploy)

Your own site

<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/deploy"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/deploy/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,131 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01131
Opus 5.5	$0.00007	$0.00452
Sonnet 5.5	$0.00004	$0.00226
Haiku 4.5	$0.00002	$0.00113

Measured 23d ago against content hash 08ec2a61576b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 23d 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.

.claude/commands/deploy.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy the workspace program(s) to the cluster in $ARGUMENTS (default devnet). Squads upgrade proposals, rollback and cost tables: deployment.md.

Devnet

solana config get and solana address: confirm the RPC URL and the deployer. Keep keypair paths under ~/.config/solana/ out of commands (the secrets hook blocks them) and rely on the configured default signer.
New program: anchor keys sync so declare_id! and Anchor.toml match target/deploy/<name>-keypair.json, then rebuild with /build-program. Skipping this gives DeclaredProgramIdMismatch at runtime.
Fund: solana airdrop 2 (rate-limited; fall back to the web faucet). Cost: solana rent <size of the .so in bytes>; the deploy needs about twice that until the buffer closes.
Deploy: anchor deploy --provider.cluster devnet, or solana program deploy target/deploy/<name>.so.
Publish the IDL; in Anchor 1.x it lives in Program Metadata: anchor idl init --filepath target/idl/<name>.json the first time, anchor idl upgrade --filepath target/idl/<name>.json after upgrades.
Verify with solana program show <PROGRAM_ID> (authority, data length) and run the integration tests against devnet.
Record the ID in .program-id-devnet and in the app env (e.g. NEXT_PUBLIC_PROGRAM_ID).

Mainnet

Start only when the user asks for mainnet, and first report which preconditions are missing: /audit-solana with no open Critical or High findings; tests and fuzzing pass; a devnet deployment exercised the real flows; the upgrade-authority plan is decided; an external audit for programs that hold user funds.

Show the user the program, deployer address and balance, estimated cost and upgrade authority, and wait for an explicit yes.
anchor build --verifiable (needs Docker; writes target/verifiable/<name>.so), then deploy that artifact: CONFIRM_MAINNET=1 anchor deploy --verifiable --provider.cluster mainnet. Plain anchor deploy would ship target/deploy/ instead. With the Solana CLI: CONFIRM_MAINNET=1 solana program deploy target/verifiable/<name>.so --url mainnet-beta --with-compute-unit-price <micro-lamports> --use-rpc, so the write transactions land under congestion.
Verify: anchor verify <PROGRAM_ID> --provider.cluster mainnet; solana program dump <PROGRAM_ID> dump.so --url mainnet-beta and diff it against the deployed file. The dump is zero-padded to the ProgramData size, so hash equal lengths: head -c $(wc -c < target/verifiable/<name>.so) dump.so | shasum -a 256 against shasum -a 256 target/verifiable/<name>.so. Confirm the upgrade authority with solana program show.
Publish the IDL (devnet step 5), then record .program-id-mainnet, deployment-mainnet.json (programId, deployedAt, deployer, upgradeAuthority, commit) and the production app env.
Smoke-test read-only paths first, then writes with minimal amounts.

Read the full file on GitHub · 43 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.

23d ago Changed · -311 lines · +5 tokens per session 08ec2a61576b
24d ago Changed 5e75be903606
1mo ago First seen · 354 lines · 13 tokens per session scan A c767f95f5e24

Subscribe to this mod's changes

deploy is a command published in the GitHub repository solanabr/solana-ai-kit (104 stars, last pushed 24d ago), licensed MIT. It adds 18 tokens to every session and 1,131 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code DevOps and cloud Web3 and blockchain claude-agent claude-commands claude-md claude-skills claude-subagents

deploy

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Devnet

Mainnet

What this file has done since we first saw it

Other commands, from other repositories

apex

explain-architecture

prompt

design-audit

amend

test