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 dappgit 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/dapp)<a href="https://agentmods.dev/skills/rylsherdamz-rgb/stellar-forge/dapp"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/dapp/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/dapp"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/dapp.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.00048 | $0.01452 |
| Opus 5 | $0.00024 | $0.00726 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
dapp 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Stellar dApp / frontend development. Covers javascript stellar-sdk, Stellar Wallets Kit, and the agentic kit data layer — useStellarData(), useContract(), useStellarWallet(). No raw RPC or curl." How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dApp — Agentic Kit Frontend
All blockchain queries go through useStellarData(). Never write raw RPC or curl.
Wallet Setup (one-time)
// providers/wallet-provider.tsx
import { WalletProvider } from "@/providers/wallet-provider";
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<WalletProvider>
{children}
</WalletProvider>
);
}
Hooks API
useStellarData() — Blockchain queries
import { useStellarData } from "@/hooks/use-stellar-data";
const {
getBalances, // (address: string) => { asset, balance }[]
queryContract, // (id: string, method: string, args: ScVal[]) => ScVal | null
getContractData, // (id: string, key: ScVal) => ScVal | null
getEvents, // (id: string, limit?: number) => Event[]
getTransaction, // (hash: string) => TxResponse | null
loading, // boolean
error, // string | null
rpc, // raw RPC client (fallback only)
} = useStellarData();
useContract(contractId) — Contract read/write
import { useContract } from "@/hooks/use-contract";
const c = useContract("CA3...");
await c.read("name"); // simulation-only, no tx
await c.read("balance_of", [addressArg]); // any read method
await c.write(sender, "transfer", args, signFn); // full sign+submit
// c.data exposes the underlying useStellarData()
useStellarWallet() — Wallet connection + data
import { useStellarWallet } from "@/hooks/use-stellar-wallet";
const {
address, // string | null
network, // string | null
connect, // () => Promise<void>
disconnect, // () => void
sign, // (xdr: string) => Promise<string>
getBalances, // () => Promise<{asset, balance}[]>
data, // useStellarData()
} = useStellarWallet();
useWallet() — From WalletProvider context
import { useWallet, useContract, useStellarData } from "@/providers/wallet-provider";
const { address, sign, data, getBalances } = useWallet();
// Same as useStellarWallet() but from context — no need to call connect()
What ships with it
10 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.
- components/connect-button.tsx 1.2 KB
- components/invoke-contract.tsx 1.7 KB
- components/send-payment.tsx 1.8 KB
- examples/dashboard-page.tsx 1.2 KB
- examples/use-stellar-data-example.tsx 2.5 KB
- hooks/use-contract.ts 1.8 KB runs code
- hooks/use-stellar-data.ts 3.8 KB runs code
- hooks/use-stellar-wallet.ts 1.4 KB runs code
- lib/stellar-config.ts 1.1 KB runs code
- providers/wallet-provider.tsx 875 B
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 · 155 lines · 48 tokens per session scan A 25241a639506
dapp is a skill published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 17d ago), licensed MIT. It adds 48 tokens to every session and 1,452 once invoked, about $0.0002 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 skills, from other repositories
blockchain-web3
Use this skill when asked about web3 frontend development, ethers.js, viem, wagmi, web3.js, wallet integration (MetaMask, Phantom, WalletConnect), dApp architecture, RPC providers (Alchemy, Infura), and TypeScript blockchain SDKs. Language: TypeScript. Covers reading blockchain state, sending transactions, wallet…
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…
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.
rail402-cli
Discover and pay for x402 APIs on Stellar from the command line. Use when an agent needs to find a paid API in the x402 Bazaar, pay for an API call with USDC on Stellar testnet, fund a testnet wallet, or look up an x402 settlement on the explorer — via the rail402 CLI.
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…