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.
curl -O https://raw.githubusercontent.com/jamesbachini/x402-mcp-stellar/main/AGENTS.mdgit clone --depth 1 https://github.com/jamesbachini/x402-mcp-stellarWrote 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/instructions/jamesbachini/x402-mcp-stellar/agents-md)<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>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.00538 | $0.00538 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Eleventts-stellar-mcp AGENTS.md — 100% identical, 0 lines differ
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 existingsrc/stellar/*modules.
Build, Test, and Development Commands
npm install: install dependencies (requires Node.js 20+).npm run dev: run the MCP server withtsxfor 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
strictcompiler 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 buildis the minimum validation gate. - For behavior changes, include manual verification steps:
- Copy
.env.exampleto.envand set wallet values. - Start facilitator and x402-protected resource server.
- Run
npm run devand exercisefetch_paid_resource.
- Copy
- If you add tests, use
*.test.tsnaming and colocate with modules or undersrc/__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.
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.
- 8d ago First seen · 39 lines · 538 tokens per session scan A 7eb1a89d697f
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.
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.
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.
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).
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).
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.
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.