x402-mcp-stellar: Instructions file for Codex

AGENTS.md

x402-mcp-stellar AGENTS.md is an instructions file for Codex, OpenCode from jamesbachini/x402-mcp-stellar. It costs 538 tokens per session, scanned A, original, MIT.

Repository instructions for an MCP server that connects x402 payments with Stellar, a blockchain network. They describe the TypeScript source layout, development commands, code style, and testing expectations.

In plain words
What is it for?
Use them when adding or changing server tools, payment protocol logic, Stellar modules, configuration, or TypeScript code in this repository.
Why use it?
They show an agent where Stellar payment code belongs and how to build and run the server consistently.

Instructions file for CodexOpenCode

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

This is jamesbachini/x402-mcp-stellar's own configuration. It tells Codex and OpenCode how to work on x402-mcp-stellar 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 x402-mcp-stellar configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jamesbachini/x402-mcp-stellar. 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/jamesbachini/x402-mcp-stellar/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/jamesbachini/x402-mcp-stellar

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 x402-mcp-stellar AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jamesbachini/x402-mcp-stellar/agents-md.svg)](https://agentmods.dev/instructions/jamesbachini/x402-mcp-stellar/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/jamesbachini/x402-mcp-stellar/agents-md"><img src="https://agentmods.dev/badge/instructions/jamesbachini/x402-mcp-stellar/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 538 This file is loaded in full into every session.
When invoked 538 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.00538 $0.00538
Opus 5 $0.00269 $0.00269
Sonnet 5 $0.00108 $0.00108
Haiku 4.5 $0.00054 $0.00054

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

Security

Grade A, and why

x402-mcp-stellar 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 39 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • src/index.ts: MCP stdio server entrypoint, tool registration, env loading, and x402 payment wiring.
  • src/stellar/: vendored Stellar payment implementation (signer, constants, shared types, utilities).
  • src/stellar/exact/{client,server,facilitator}/: exact scheme protocol logic and adapters.
  • Root config/files: package.json, tsconfig.json, .env.example, README.md.
  • Keep new features in src/; place Stellar-specific logic alongside existing src/stellar/* modules.

Build, Test, and Development Commands

  • npm install: install dependencies (requires Node.js 20+).
  • npm run dev: run the MCP server with tsx for local development.
  • npm run start: run the server in a production-like mode with source maps.
  • npm run build: TypeScript type-check only (tsc --noEmit); run this before opening a PR.

Coding Style & Naming Conventions

  • Language: TypeScript (ES modules) with strict compiler settings.
  • Formatting in current codebase: 2-space indentation, semicolons, double quotes.
  • File/module naming: lowercase, descriptive names (for example signer.ts, constants.ts).
  • Prefer explicit, descriptive function names (for example getRequiredEnv, tryParseBody) and clear types on exported APIs.

Testing Guidelines

  • No dedicated test runner is configured yet; npm run build is the minimum validation gate.
  • For behavior changes, include manual verification steps:
    1. Copy .env.example to .env and set wallet values.
    2. Start facilitator and x402-protected resource server.
    3. Run npm run dev and exercise fetch_paid_resource.
  • If you add tests, use *.test.ts naming and colocate with modules or under src/__tests__/.

Commit & Pull Request Guidelines

  • Use concise, imperative commit subjects, consistent with history (for example resource agnostic, Update README.md).
  • Keep commit subjects focused and under ~72 characters.
  • PRs should include: purpose, key changes, config/env impact, and verification commands/results.
  • Link related issues and include request/response examples when MCP tool behavior changes.

Read the full file on GitHub · 39 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 · 39 lines · 538 tokens per session scan A 7eb1a89d697f

Subscribe to this mod's changes

x402-mcp-stellar AGENTS.md is an instructions file published in the GitHub repository jamesbachini/x402-mcp-stellar (2 stars, last pushed 4mo ago), licensed MIT. It adds 538 tokens to every session, about $0.0027 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.

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

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens