stoa AGENTS.md

An entry point of rules for the STOA platform, a system with cloud control services and on-premise data services, used by coding agents.

In plain words
What is it for?
It guides work across the main repository, individual services, and on-demand technical documentation.
Why use it?
It tells agents where the authoritative project rules live and which service-specific instructions to read before editing code.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/stoa-platform/stoa/agents-md
Clone the repo
git clone --depth 1 https://github.com/stoa-platform/stoa

Made for: Codex, OpenCode.

Per session 529 This file is loaded in full into every session.
When invoked 529 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00529 $0.00529
Opus 5 $0.00264 $0.00264
Sonnet 5 $0.00106 $0.00106
Haiku 4.5 $0.00053 $0.00053

Measured 2d ago against content hash f1d34ef93fc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

stoa 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 2d 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 · 53 lines

What it actually says

AGENTS.md — STOA Platform

This repo uses CLAUDE.md as the canonical AI agent contract. AGENTS.md exists as the cross-agent entry point for any AI coding assistant (Claude Code, Codex, Cursor, Aider, etc.).

Contract

AI agents working in this repository must:

  1. Read CLAUDE.md at the repo root for project rules, architecture, runtime versions, workflow, and GO/NOGO gates. It is the single source of truth — this file does not duplicate its content to avoid drift.
  2. Read the component-scoped CLAUDE.md inside the directory you are editing (e.g. stoa-gateway/CLAUDE.md, control-plane-api/CLAUDE.md, control-plane-ui/CLAUDE.md) when touching that service.
  3. Load .claude/docs/<topic>.md on demand when a rule in CLAUDE.md references it. These docs are protocols, examples, and gotcha tables — never auto-loaded, only pulled in when the topic is in scope.
  4. Follow the same rules regardless of the tool brand. The .claude/ storage path is a naming convention, not a tool lock-in; any AI agent is expected to honor the rules defined there.

Architecture (quick reference)

CONTROL PLANE (Cloud)                    DATA PLANE (On-Premise)
┌────────────────────────────┐           ┌──────────────────────┐
│ Portal  Console  API  Auth │  ←sync→   │ STOA GW webMethods   │
│ (React) (React) (Py) (KC) │           │ (Rust)  Kong/Envoy   │
└────────────────────────────┘           └──────────────────────┘

For component paths, runtime versions, RBAC roles, rules, skills, and repo map, see CLAUDE.md.

Agent-facing API doctrine

When touching an API operation exposed to agents, load the canonical rule in CLAUDE.md and .claude/docs/uac-llm-ready.md:

UAC describes.
MCP projects.
Smoke proves.

Historical note

The Python mcp-gateway/ service was retired in Feb 2026 and superseded by stoa-gateway/ (Rust). Any reference to mcp-gateway in older docs or comments is historical.

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. 2d ago First seen · 53 lines · 529 tokens per session scan A f1d34ef93fc1

Subscribe to this mod's changes

stoa AGENTS.md is an instructions file published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 529 tokens to every session, about $0.0026 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.