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 skills add rylsherdamz-rgb/stellar-forge --skill datagit 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/skills/rylsherdamz-rgb/stellar-forge/data)<a href="https://agentmods.dev/skills/rylsherdamz-rgb/stellar-forge/data"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/data/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/skills/rylsherdamz-rgb/stellar-forge/data"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00575 |
| Opus 5.5 | $0.00016 | $0.00230 |
| Sonnet 5.5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
data 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
All blockchain queries use `useStellarData()` (frontend) or Stellar SDK / RPC directly (backend). Never raw curl or manual RPC calls. How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data — Stellar Chain Queries
All blockchain queries use useStellarData() (frontend) or Stellar SDK / RPC directly (backend). Never raw curl or manual RPC calls.
Source Files (published with this skill)
| File | Contents |
|---|---|
templates/src/index.ts |
Express server — balance endpoint, contract query endpoint, CORS |
templates/src/services/stellar.ts |
RPC client — getBalances, queryContract, getContractData, getEvents, getTransaction |
Agentic Kit (Frontend)
Import from @/hooks/use-stellar-data:
const { getBalances, queryContract, getContractData, getEvents, getTransaction, loading, error } = useStellarData();
| Method | Returns | Description |
|---|---|---|
getBalances(address) |
{asset, balance}[] |
All trustline balances + native XLM |
queryContract(contractId, method, args[]) |
ScVal | null |
Read-only contract query (simulation) |
getContractData(contractId, key) |
ScVal | null |
Raw contract storage entry |
getEvents(contractId, limit?) |
Event[] |
Contract events (newest first) |
getTransaction(hash) |
TxResponse | null |
Check tx status + return value |
Backend / API
Use the Stellar SDK directly:
import { rpc } from "@/lib/stellar-config";
const account = await rpc.getAccount(address);
const sim = await rpc.simulateTransaction(tx);
const sent = await rpc.sendTransaction(signedTx);
const events = await rpc.getEvents({ contractIds: [contractId] });
Raw RPC (if needed)
rpc.getLedgerEntries(keys)— raw ledger datarpc.getNetwork()— network inforpc.getLatestLedger()— current ledger seq- Horizon:
GET /accounts/{id},GET /claimable_balances,GET /payments
Strict Rules
- Frontend: always use
useStellarData()— never raw RPC or curl - Read-only contract state: use
useContract().read()(simulation, no tx) - State-changing contract calls: use
useContract().write()(sign + submit) - Backend: use
rpc.*methods directly for server-side queries
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 58 lines · 41 tokens per session scan A 0dbd04b1a3ca
data is a skill published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 575 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
nirium-agentic-payments
Scaffold and run an x402 paid API server on Stellar with open-source client libraries: charge AI agents per API call with x402Serve(), a function from the nirium SDK that runs entirely on your own server, scaffold that server with nirium-cli in one command, and separately read live protocol data through the nirium-mcp…
x402-stellar-payments
Use when asked to "pay for" a URL, add a "paid endpoint", handle HTTP 402, or work with x402 payments on Stellar.
mcp
Use when an AI agent or MCP client needs to discover, rank, inspect evidence limits, and inspect self-declared service endpoint candidates for Stellar 8004 agents at runtime. Documents how to register the read-only, keyless stellar-agent-search server and use its tools, resources, and prompts; reputation values remain…
averray-worker
Use Averray's MCP workflow to sign in with your own wallet, choose eligible work, claim and submit it, confirm settlement, and withdraw earnings.
averray-poster
Use Averray's MCP workflow to draft and fund a job from your own wallet, select an honest verifier path, and understand settlement, receipts, cancellation, and disputes.