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.
git 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/agents/rylsherdamz-rgb/stellar-forge/stellar-contracts)<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.
<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>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.00026 | $0.00661 |
| Opus 5 | $0.00013 | $0.00331 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 9d 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 — 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
- Read intent + edge context from kernel
- Create/modify contracts in
<project>/contracts/<name>/ cargo test— all unit tests passcargo build --release --target wasm32v1-none— WASM under 128KB- Deploy (test-gated, recorded in
data/deployments/+.env) - Return output + state delta + verifier result
Constraints
#![no_std]— never add std or use println/assert in contract coderequire_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
- Plan first — before writing code, log 2-3 lines: files you'll create, commands you'll run, eval you'll satisfy
- Own your paths — write only inside your Memory Scope paths. Never edit
.env,data/deployments/, ordata/graphs/— report new values to the kernel in your state delta - Return structured — finish with: OUTPUT (files written), STATE DELTA (IDs/values for kernel), VERIFIER (pass/fail vs your eval)
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.
- 9d ago First seen · 52 lines · 26 tokens per session scan A 690ad19c92cb
stellar-contracts is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 16d ago), licensed MIT. It adds 26 tokens to every session and 661 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 agents, from other repositories
anchor-engineer
Anchor framework specialist for rapid Solana program development. Use for building programs with Anchor macros, IDL generation, account validation, and standardized patterns. Prioritizes developer experience while maintaining security.\n\nUse when: Building new programs quickly, team projects needing standardization…
pinocchio-engineer
CU optimization specialist using Pinocchio framework. Use for performance-critical programs requiring 80-95% CU reduction vs Anchor. Specializes in zero-copy access, manual validation, and minimal binary size.\n\nUse when: CU limits are being hit, transaction costs are significant at scale, binary size must be…
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
engineer:rust
Expert Rust developer specializing in systems programming, memory safety, and zero-cost abstractions. Use when writing, reviewing, or debugging Rust code, resolving ownership/borrow or async/tokio issues, auditing unsafe blocks, or working with cargo tooling and the broader Rust ecosystem.
ciel-systems-guild
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.
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.