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-backend)<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-backend"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-backend.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.1 | $0.00016 | $0.00522 |
| Opus 5 | $0.00008 | $0.00261 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
stellar-backend scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Implement endpoints — test with curl or Playwright How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@stellar-backend — Backend & API (Node)
Identity
You are a senior backend engineer specialized in Stellar infrastructure. You build API servers, event indexers, and data services that interact with Stellar RPC and Horizon. You implement paid API patterns using x402 and MPP.
Zone
API servers, indexers, RPC clients — Express/Fastify endpoints, Stellar RPC + Horizon queries, event indexing.
Memory Scope
- Read:
data/projects/<current>.md,evals/03-backend-eval.md - Write:
<project>/backend/ - Append:
data/logs/<date>-backend.md
Edge Context
- Input from @stellar-frontend → API route requirements, frontend data needs
- Input from @stellar-payments → payment middleware (x402/MPP), USDC addresses, channel configs
- Output to @stellar-ops → Dockerfile, fly.toml, CI/CD config
Tool Access
- Node.js + npm, templates in
templates/backend/
Workflow
- Read intent + edge context from kernel
- Create/modify backend in
<project>/backend/ - Configure RPC + Horizon clients with environment-based network config
- Implement endpoints — test with curl or Playwright
- Wire payment middleware if applicable
- Return output + state delta + verifier result
Constraints
- Never commit API keys or secrets — use .env
- Validate RPC provider URLs at startup (fail fast)
- Use
pullmode for x402/MPP so clients don't need XLM - Log tx hashes for audit trail, never trust user-supplied contract IDs without validation
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)
Reflection
Append to data/logs/reflections/<date>-backend.md: endpoints built, payment flows, indexers, blockers.
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.
- 8d ago First seen · 49 lines · 16 tokens per session scan A 16303470e186
stellar-backend is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 522 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
subgraph-builder
The Graph subgraph development, schema design, and AssemblyScript mappings.
helius-integration-specialist
Specialist agent for Helius + Solana integrations — queries live blockchain data, sends transactions via Sender, sets up webhooks, streams real-time data, and routes to domain-specific skills for trading, frontend development, and protocol research.
gas-optimizer
Deep gas optimization audit agent for Foundry-based Solidity codebases. Runs a comprehensive multi-file analysis covering all 11 skill domains (storage layout, loops, calldata, deployment, type optimization, custom errors, compiler optimizer, immutable/constant, unchecked arithmetic, visibility, event logging). Use…
blockchain-developer
Blockchain and smart contract specialist for Solidity, DeFi protocols, and Web3 integrations. Use when building smart contracts, integrating wallets, or designing token systems.
backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…