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 stellar-mcpgit 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/stellar-mcp)<a href="https://agentmods.dev/skills/rylsherdamz-rgb/stellar-forge/stellar-mcp"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/stellar-mcp/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/stellar-mcp"><img src="https://agentmods.dev/badge/skills/rylsherdamz-rgb/stellar-forge/stellar-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 78 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00061 | $0.00735 |
| Opus 5 | $0.00030 | $0.00367 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
stellar-mcp 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stellar MCP Tools
Claude has direct access to the Stellar blockchain, filesystem, and GitHub through MCP servers configured in .mcp.json.
Available MCP Servers
stellar-rpc
Direct blockchain queries without leaving the conversation.
Tools available:
- get_account(address) → account balance, sequence, signers
- get_contract_data(id, key) → contract storage entry
- simulate_transaction(xdr) → simulate before submitting
- send_transaction(xdr) → submit signed transaction
- get_events(contractId) → query contract events
- get_ledger_entries(keys) → raw ledger entries
Use for:
- Checking account balances during development
- Verifying contract state after deployment
- Debugging transaction failures with simulation
- Querying contract events without writing frontend code
filesystem
Read and write project files directly.
Tools available:
- read_file(path) → read file contents
- write_file(path) → write file contents
- list_directory(path) → list files in directory
- search_files(pattern) → search by glob
- get_file_info(path) → file metadata
github
Manage repositories, PRs, issues, and code search.
Tools available:
- create_or_update_file → commit changes
- search_repositories → find repos
- get_issue → read issue details
- create_pull_request → open PRs
- list_issues → browse open issues
playwright
Run browser-based e2e tests for Stellar dApps.
Tools available:
- browser_navigate(url) → open page
- browser_click(selector) → click element
- browser_type(selector, text) → fill input
- browser_screenshot() → capture screen
- browser_evaluate(script) → run JS in page
When to Use MCP vs Agentic Kit
| Task | Use |
|---|---|
| Query chain data during development | stellar-rpc MCP |
| Check contract state after deploy | stellar-rpc MCP |
| Read/write project files | filesystem MCP |
| Commit and push code | github MCP |
| Run e2e tests | playwright MCP |
| Production frontend blockchain queries | useStellarData() hook |
| Production contract calls from frontend | useContract().write() hook |
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.
- 12d ago First seen · 101 lines · 61 tokens per session scan A 3e39e6fb7584
stellar-mcp is a skill published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 735 once invoked, about $0.0003 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 skills, from other repositories
Web3 & Blockchain Development
Production-grade Web3 development with Solidity smart contracts, ethers.js/web3.js integration, DApp architecture, security patterns, and AI-enhanced blockchain development (ChatWeb3, Aider + Gemini 2024).
sui-move-security-review
Use when auditing, reviewing, or hunting for vulnerabilities in Move code on Sui. Applies equally to source code (.move files) and to disassembly of compiled bytecode (on-chain packages). A checklist of invariants whose VIOLATION causes exploitable bugs: access control & capabilities, struct abilities & type safety…
move-bytecode-comprehension
Use when reading or reasoning about compiled Move bytecode or sui move disassemble output. Mental model for the binary format, what survives compilation (and what's lost), and how to read disassembly soundly. Trigger on "what does this package do?", "read this .mv module", "interpret this disassembly", or whenever an…
official-sui-skills
Pointer to the official Mysten Labs skills for building on Sui — language fundamentals, object model, PTBs, SDKs, publishing, upgrades, frontend integration, accessing on-chain data. Maintained upstream at github.com/MystenLabs/skills; pinned to the same ref the audit catalog derives from (see…
sui-and-move-tools
Use to get bytecode for a deployed Sui package and produce a disassembled working view. One GraphQL call fetches every module's raw bytecode bytes; sui move disassemble (already on the system, running sui prompt) produces .asm files for analysis. Trigger on "fetch this package's bytecode", "get me the .mv for package…
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…