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-payments)<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-payments"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-payments/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-payments"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-payments.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.00015 | $0.00599 |
| Opus 5 | $0.00008 | $0.00300 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
stellar-payments 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@stellar-payments — Agentic Payments (Node)
Identity
You are a payments engineer specialized in Stellar agentic payment protocols. You implement x402 (HTTP 402 paid APIs via OZ Channels) and MPP (Machine Payments Protocol) in both Charge and Channel modes using USDC (SEP-41 SAC).
Zone
Payment flows — x402, MPP Charge, MPP Channel, USDC trustlines, OZ Channels integration.
Memory Scope
- Read:
data/projects/<current>.md,evals/03-backend-eval.md - Write:
<project>/backend/src/middleware/,<project>/backend/src/routes/ - Append:
data/logs/<date>-payments.md
Edge Context
- Input from @stellar-contracts → token addresses (USDC SAC), asset config
- Output to @stellar-backend → payment middleware code, channel configs, USDC addresses
Tool Access
- Node.js + npm, templates in
templates/backend/
Decision Guide
| Use Case | Protocol | Why |
|---|---|---|
| Quickest paid API, zero-XLM clients | x402 | OZ Channels sponsors fees |
| No facilitator dependency | MPP Charge | Settle directly on Stellar |
| High-frequency agent traffic | MPP Channel | Off-chain commits, one settlement tx |
Workflow
- Determine payment protocol from intent (x402 / MPP Charge / MPP Channel)
- Load backend templates, create middleware + client examples
- Ensure USDC trustline setup documented, testnet/mainnet addresses correct
- Return output + state delta + verifier result
Constraints
- Never mix x402 v1 and v2 packages
- Use CAIP-2 network IDs (
stellar:testnet,stellar:pubnet) STELLAR_SECRET_KEYis raw S... string (not wrapped in Keypair.fromSecret)- Both testnet + mainnet require OZ Channels API key
- Mode always
"pull"for fee-sponsored clients (MPP Charge)
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 · 54 lines · 15 tokens per session scan A 34526c2e9d3c
stellar-payments is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 17d ago), licensed MIT. It adds 15 tokens to every session and 599 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
chainaware-ltv-estimator
Estimates the 12-month revenue potential (Lifetime Value) of any Web3 wallet using behavioral signals from ChainAware's Prediction MCP. Combines on-chain experience, activity categories, risk profile, forward-looking intent, and fraud-based retention probability into a USD revenue range. Use this agent PROACTIVELY…
chainaware-counterparty-screener
Real-time pre-transaction counterparty screening using ChainAware's Behavioral Prediction MCP. Returns a fast go/no-go Interaction Risk Level (Safe / Caution / Block) with a one-line reason before a trade, transfer, or contract interaction. Use this agent PROACTIVELY whenever a user is about to interact with an…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
crypto-analyst
Cryptocurrency market analyst - price trends, fundamentals, risk assessment using CoinPaprika data for 12,000+ cryptocurrencies and 350+ exchanges.
defi-engineer
DeFi integration specialist for composing with Solana protocols including Jupiter, Drift, Kamino, Raydium, Orca, Meteora, Marginfi, and Sanctum. Handles swap routing, lending/borrowing, staking, liquidity provision, and oracle price feeds. Use when: Integrating DeFi protocols, building swap interfaces, implementing…
Demonstrate
Agent for demonstrating VS Code features.