agentmods.dev

Stellar-mcp: Instructions file for Codex

AGENTS.md

Stellar-mcp AGENTS.md is an instructions file for Codex, OpenCode from JulioMCruz/Stellar-mcp. It costs 996 tokens per session, scanned A, original, MIT.

Repository instructions for agents working with Stellar and Soroban, Stellar’s smart-contract platform. They cover code, testing, secret handling, branches, commits, and pull requests.

In plain words
What is it for?
They are for building Soroban contracts in Rust, testing them, preparing Stellar frontends, and following the repository’s Git and security practices.
Why use it?
They give an agent project-specific rules that reduce unsafe changes, leaked secrets, and unreviewed code.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is JulioMCruz/Stellar-mcp's own configuration. It tells Codex and OpenCode how to work on Stellar-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Stellar-mcp configures →

not rated 0repo 2mo ago A scan 996 tokens original MIT
View source ↗ JulioMCruz/Stellar-mcp
Reuse

Borrowing it

Nothing to install: this file belongs to JulioMCruz/Stellar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JulioMCruz/Stellar-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/JulioMCruz/Stellar-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Stellar-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/juliomcruz/stellar-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/juliomcruz/stellar-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/juliomcruz/stellar-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/juliomcruz/stellar-mcp/agents-md/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.

agentmods 80×15 button for Stellar-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/juliomcruz/stellar-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/juliomcruz/stellar-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 996 This file is loaded in full into every session.
When invoked 996 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00996 $0.00996
Opus 5 $0.00498 $0.00498
Sonnet 5 $0.00199 $0.00199
Haiku 4.5 $0.00100 $0.00100

Measured 8d ago against content hash 9cf3086aba18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

Stellar-mcp AGENTS.md 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 8d 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.

AGENTS.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md - Stellar MCP Agent Instructions

These instructions are for coding agents working in this repository or using this MCP server to generate Stellar/Soroban app code.

Git Safety

  • Work on a feature branch. Do not commit directly to main.
  • Open a pull request for review. Do not merge without Julio's explicit approval.
  • Before every commit, run git diff --cached and check for secrets.
  • Never commit secret seeds, private keys, wallet mnemonics, PATs, API keys, .env files, server IPs, or private infrastructure notes.
  • Use placeholders such as <STELLAR_SECRET_KEY>, <CONTRACT_ID>, <PUBLIC_KEY>, and <RPC_URL> in docs and examples.

Soroban Contract Code

  • Use Rust and soroban-sdk for Soroban contracts.
  • Start new contracts with stellar_soroban_scaffold_contract unless the user asks for a different layout.
  • Keep contracts #![no_std].
  • Keep contract state explicit. Prefer clear persistent or temporary storage keys over hidden/global state.
  • Add unit tests under the contract crate before proposing deploy steps.
  • Use cargo test for logic tests and stellar contract build for WASM builds.
  • Use wasm32v1-none as the WASM target in new build instructions.
  • Do not hand-roll deployment transactions when Stellar CLI or existing MCP tools can do it.
  • For deployed contract frontends, generate TypeScript bindings with stellar contract bindings typescript and use those bindings from Next.js.

Stellar Frontend Code

  • Use stellar_nextjs_wallet_scaffold for new Next.js wallet components.
  • Keep wallet code client-side with "use client".
  • Use Freighter for browser wallet connection and transaction signing unless the user asks for another wallet strategy.
  • Local Freighter testing should use a secure browser context, for example next dev --experimental-https.
  • Never expose server secrets through NEXT_PUBLIC_*.
  • NEXT_PUBLIC_* values are only for public network, RPC, Horizon, and contract IDs.
  • Keep transaction signing in the wallet. Do not put secret seeds in a Next.js app.
  • For test wallets, use stellar_generate_test_wallet or the generated scripts/create-test-wallet.mjs --fund; store seeds only in .env.local or a secret manager.
  • Never commit test wallet seeds. Testnet secrets are still secrets.
  • After deploying a contract, set NEXT_PUBLIC_STELLAR_CONTRACT_ID, generate TypeScript bindings, and import those bindings into the UI instead of hand-writing XDR.
  • Smart contract UI work must include contract tests plus at least one UI/build/typecheck path showing the generated bindings are wired.

Read the full file on GitHub · 65 lines

Changes

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.

  1. 8d ago First seen · 65 lines · 996 tokens per session scan A 9cf3086aba18

Subscribe to this mod's changes

Stellar-mcp AGENTS.md is an instructions file published in the GitHub repository JulioMCruz/Stellar-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 996 tokens to every session, about $0.0050 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-31.

Web3 and blockchain
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens