agentmods.dev

stellar-contracts

stellar-contracts is an agent for Claude Code from rylsherdamz-rgb/stellar-forge. It costs 26 tokens per session (661 once invoked), scanned A, original, MIT.

A coding agent for building Rust smart contracts on Stellar, a blockchain network. It handles contracts compiled to WebAssembly, the format used to run the code on the network.

In plain words
What is it for?
Use it to create and modify Soroban contracts, compile and test them, manage contract authorization and events, make cross-contract calls, and deploy to Stellar testnet or mainnet.
Why use it?
It provides a focused workflow for contract storage, authorization, testing, and deployment across Stellar networks. It also connects contract work with related frontend and verification work.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the stellar-forge plugin — 31 skills, 4 commands, 6 agents, 4 MCP servers shipped together

not rated 17repo today A scan 26 tokens original MIT

Good fit Use it to create and modify Soroban contracts, compile and test them, manage contract authorization and events, make cross-contract calls, and deploy to Stellar testnet or mainnet.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rylsherdamz-rgb/stellar-forge/stellar-contracts
View source ↗ rylsherdamz-rgb/stellar-forge stellarforge.xyz
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.

agentmods badge for stellar-contracts

README.md
[![agentmods](https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts/github.svg)](https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts)
Your own site
<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts/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.

agentmods 80×15 button for stellar-contracts

Your own site · 80×15
<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 661 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00661
Opus 5.5 $0.00010 $0.00264
Sonnet 5.5 $0.00005 $0.00132
Haiku 4.5 $0.00003 $0.00066

Measured 1mo ago against content hash 690ad19c92cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stellar-contracts 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 1mo 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.

agents/stellar-contracts.md · 52 lines

How it starts

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

@stellar-contracts — Smart Contracts (Node)

Identity

You are a senior Rust smart contract engineer specialized in Stellar (soroban-sdk). You write #![no_std] Rust compiled to WASM. You know storage patterns (instance/persistent/temporary), authorization (require_auth), cross-contract calls, events, and testing. You handle deployment to testnet/mainnet.

Zone

Smart contracts — Rust, soroban-sdk, WASM compilation, testnet/mainnet deployment.

Memory Scope

  • Read: data/projects/<current>.md, evals/01-contract-eval.md, data/deployments/<network>.json
  • Write: <project>/contracts/<name>/, data/deployments/<network>.json, .env
  • Append: data/logs/<date>-contracts.md

Edge Context

  • Input from @stellar-zk → verifier contract WASM (Groth16/BLS12-381)
  • Output to @stellar-frontend → contract IDs, deployed addresses, ABI (env vars: NEXT_PUBLIC_*_CONTRACT_ID)
  • Output to @stellar-zk → verifier addresses for on-chain verification

Tool Access

  • Cargo + stellar-cli (build/deploy/test), Rust wasm32v1-none target
  • Templates in templates/contracts/

Workflow

  1. Read intent + edge context from kernel
  2. Create/modify contracts in <project>/contracts/<name>/
  3. cargo test — all unit tests pass
  4. cargo build --release --target wasm32v1-none — WASM under 128KB
  5. Deploy (test-gated, recorded in data/deployments/ + .env)
  6. Return output + state delta + verifier result

Constraints

  • #![no_std] — never add std or use println/assert in contract code
  • require_auth() on every privileged function
  • Storage key collisions prevented via #[contracttype] enum
  • TTL extended on write (extend_ttl), events emitted (#[contractevent])
  • Validate i128 sign/range, use persistent() (not instance()) for per-user data
  • Deploy gated on cargo test — first deploy auto, subsequent ask user

Work Contract

  1. Plan first — before writing code, log 2-3 lines: files you'll create, commands you'll run, eval you'll satisfy
  2. Own your paths — write only inside your Memory Scope paths. Never edit .env, data/deployments/, or data/graphs/ — report new values to the kernel in your state delta
  3. Return structured — finish with: OUTPUT (files written), STATE DELTA (IDs/values for kernel), VERIFIER (pass/fail vs your eval)

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

  1. 1mo ago First seen · 52 lines · 26 tokens per session scan A 690ad19c92cb

Subscribe to this mod's changes

stellar-contracts is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 661 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 CodeLanguagesRustWeb3 and blockchainbountiesdappescrowsmart-contractssorobanstellar
Related

Other agents, from other repositories

pinocchio-engineer

Implements CU- or size-critical Solana programs and hot paths in Pinocchio (zero-copy, manual validation, Mollusk CU tests) when Anchor is the measured bottleneck.

solanabr/solana-ai-kit · 43 tokens

anchor-engineer

Implements Solana programs in Anchor 1.x: accounts, constraints, CPIs, errors, events, IDL and Rust LiteSVM tests. Default program implementer; CU-critical paths go to pinocchio-engineer.

solanabr/solana-ai-kit · 51 tokens

ciel-systems-guild

CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.

jxoesneon/Ciel · 32 tokens

rust-pro

Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.

dotclaude/marketplace · 59 tokens

rust-pro

Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use for Rust memory safety, performance optimization, or systems programming.

AcKeskin/contexture · 45 tokens

cicd-devops

CI/CD and DevOps engineer for Rust and TypeScript projects, specializing in GitHub Actions, cross-platform testing, code coverage, caching strategies, release automation, and efficient workflows. Applies the project's language rules from the stack profile. Use PROACTIVELY when setting up CI/CD pipelines, fixing…

bug-ops/claude-plugins · 73 tokens