A command for deploying Stellar smart contracts and related frontend or backend components. Stellar is a blockchain network, and a smart contract is code deployed to that network.

It deploys contracts to testnet, mainnet, or a local network, optionally deploys the frontend and backend, records contract IDs, and creates a project graph afterward.

It groups the build, key setup, deployment, hosting, recording, and post-deployment steps needed to publish a project.

deploy — Command for Claude Code by rylsherdamz-rgb/stellar-forge

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/rylsherdamz-rgb/stellar-forge

Made for: Claude Code.

Or install stellar-forge, the plugin that ships this one along with the rest of its 31 skills, 4 commands, 6 agents, 4 MCP servers.

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/rylsherdamz-rgb/stellar-forge/deploy/github.svg)](https://agentmods.dev/commands/rylsherdamz-rgb/stellar-forge/deploy)

Your own site

<a href="https://agentmods.dev/commands/rylsherdamz-rgb/stellar-forge/deploy"><img src="https://agentmods.dev/badge/commands/rylsherdamz-rgb/stellar-forge/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/rylsherdamz-rgb/stellar-forge/deploy"><img src="https://agentmods.dev/badge/commands/rylsherdamz-rgb/stellar-forge/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 366 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.00000	$0.00366
Opus 5.5	$0.00000	$0.00146
Sonnet 5.5	$0.00000	$0.00073
Haiku 4.5	$0.00000	$0.00037

Measured 2mo ago against content hash 40a5aa92598d, 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 2mo 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 · 37 lines

What it actually says

/deploy

Deploy Stellar contracts to a target network.

Usage

/deploy <project-path> [network] [component]

network: testnet (default), mainnet, local
component: contracts (default), frontend, backend, all

Steps

Contracts

Build: stellar contract build --manifest-path <project>/contracts/<name>/Cargo.toml
Generate or use existing key: stellar keys generate deployer --network <network> --fund (testnet/local)
Deploy: stellar contract deploy --wasm target/wasm32v1-none/release/<name>.wasm --source-account deployer --network <network>
Record contract IDs in data/projects/<name>-deployment.md

Frontend

Build: npm --prefix <project>/frontend run build
Deploy to Vercel: npx vercel --prod (requires VERCEL_TOKEN)
Or deploy to Cloudflare Pages/Docker

Backend

Docker build: docker build -t <name>-backend <project>/backend/
Push and deploy to target (fly.io, railway, etc.)

Post-Deploy

Write deployment record to data/decisions/<date>-deploy-<network>.md
Run /graphify <project> --no-viz to graph the deployed project
Report contract IDs and URLs

Warnings

Never use --network mainnet without explicit user confirmation
Never commit deployed contract IDs without user review
Testnet resets quarterly — always verify before relying on testnet state

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.

2mo ago First seen · 37 lines · 0 tokens per session scan A 40a5aa92598d

Subscribe to this mod's changes

deploy is a command published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 tokens. 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 bounties dapp escrow smart-contracts soroban stellar

deploy