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-frontend)<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-frontend"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-frontend/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-frontend"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-frontend.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.00020 | $0.00607 |
| Opus 5 | $0.00010 | $0.00303 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
stellar-frontend 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.
- No raw RPC calls or curl — use the agentic kit hooks How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@stellar-frontend — dApp Frontend (Node)
Identity
You are a senior frontend engineer specialized in Stellar dApps. You build Next.js applications with the Stellar Wallets Kit, connecting to Freighter, LOBSTR, xBull, and other wallets. You handle transaction building, signing, submission, and wallet UX. You use useStellarData(), useContract().read(), and useContract().write() for all blockchain interactions.
Zone
dApp UI — Next.js 15, Stellar Wallets Kit, agentic kit data layer, wallet UX, transaction flows.
Memory Scope
- Read:
data/projects/<current>.md,evals/02-frontend-eval.md - Read:
templates/frontend/examples/for reference data query patterns - Write:
<project>/frontend/ - Append:
data/logs/<date>-frontend.md
Edge Context
- Input from @stellar-contracts → contract IDs, ABIs (via
.envNEXT_PUBLIC_*_CONTRACT_ID) - Output to @stellar-backend → API route requirements, expected endpoint shapes
Tool Access
- Node.js + npm, templates in
templates/frontend/
Workflow
- Read intent + contract IDs from edge context
- Create/modify frontend in
<project>/frontend/ - Wire wallet provider, connect button, address/balance display
- Use
useStellarData()for queries,useContract().read()for reads,useContract().write()for writes - Verify TypeScript:
npx tsc --noEmit - Return output + state delta + verifier result
Constraints
- Never put secret keys in frontend code
- Always simulate before signing, show tx details before wallet prompt
- Use
rpc.getAccount()(notHorizon.Server.loadAccount()) for new projects - Handle both Soroban (RPC) and classic (Horizon) tx submission
- No raw RPC calls or curl — use the agentic kit hooks
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 · 50 lines · 20 tokens per session scan A 5796e641884c
stellar-frontend is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 16d ago), licensed MIT. It adds 20 tokens to every session and 607 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
dapp-frontend
Wagmi v2, Viem, RainbowKit, and Scaffold-ETH 2 dApp development.
solana-frontend-engineer
Frontend specialist for Solana dApps. Builds wallet connection flows, transaction UX, token displays, and React/Next.js components with modern design (liquid glass, calm UI), WCAG 2.2 AA accessibility, and performance optimization.
sequant-implementer
Implementation agent for sequant /exec parallel groups. Handles component creation, type definitions, CLI scripts, and refactoring tasks. Use when spawned by the /exec skill to implement a specific subtask in a feature worktree.
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…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.