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/rylsherdamz-rgb/stellar-forge/deploygit clone --depth 1 https://github.com/rylsherdamz-rgb/stellar-forgeWrote 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/rylsherdamz-rgb/stellar-forge/deploy)<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="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.00000 | $0.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 5d 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.
What it actually says
/deploy
Deploy Stellar contracts to a target network.
Usage
/deploy <project-path> [network] [component]
network:testnet(default),mainnet,localcomponent: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-vizto graph the deployed project - Report contract IDs and URLs
Warnings
- Never use
--network mainnetwithout explicit user confirmation - Never commit deployed contract IDs without user review
- Testnet resets quarterly — always verify before relying on testnet state
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.
- 5d ago First seen · 37 lines · 0 tokens per session scan A 40a5aa92598d
deploy is a command published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 12d 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.
Other commands, from other repositories
update
The update command updates the node's Docker images to their latest versions.
reset
The reset command resets a node, optionally including its configuration and data.
restart
The restart command stops and then starts a node, restarting all services.
setup
The setup command initializes a new Dash node with the specified configuration preset.
start
The start command launches a Dash node and its associated services.
stop
The stop command shuts down a running Dash node and its associated services.