astonish AGENTS.md

Repository instructions for Astonish, an AI-agent platform written mainly in Go with a React web interface. They describe the project layout, setup, and commands for building, testing, and linting.

In plain words
What is it for?
Understanding the repository structure, choosing where code belongs, starting the project, and running its build, test, and lint checks.
Why use it?
They help an agent find the right subsystem and follow stricter local rules before changing a large project with several interfaces and execution backends.

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/sap/astonish/agents-md
Clone the repo
git clone --depth 1 https://github.com/SAP/astonish

Made for: Codex, OpenCode.

Per session 2,347 This file is loaded in full into every session.
When invoked 2,347 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.02347 $0.02347
Opus 5 $0.01174 $0.01174
Sonnet 5 $0.00469 $0.00469
Haiku 4.5 $0.00235 $0.00235

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

Security

Grade A, and why

astonish 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 3d 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 · 137 lines

How it starts

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

AGENTS.md

Project overview

Astonish is an AI-agent platform distributed as one Go binary. It supports a local coding TUI, a remote multi-tenant chat/platform, HTTP/SSE APIs, reusable flows, tools/MCP, memory, browser automation, fleet orchestration, and isolated execution through Incus, Kubernetes, or OpenShell backends. The Studio UI is a React SPA embedded into the Go binary.

The repository is primarily:

  • Go 1.26 (go.mod, toolchain go1.26.1) for the CLI, agent runtime, API, storage, TUI, and sandbox backends.
  • React 19 + TypeScript/legacy JSX + Vite + Tailwind CSS 4 under web/.
  • Ent for scoped persistence, with SQLite for personal/development use and PostgreSQL for the multi-tenant platform.

Before changing a subsystem, read the nearest nested AGENTS.md; those files contain stricter subsystem-specific contracts and override this root guide.

Repository map

  • main.go, cmd/astonish/ — binary entry point and CLI dispatch. Commands should parse arguments and delegate; keep business logic in pkg/. Preserve local/remote command gating. Bare astonish launches local code mode in a TTY.
  • pkg/agent/ — LLM-driven agent loop, prompt construction, tool execution, compaction, delegation, and approvals.
  • pkg/api/ — platform/Studio HTTP handlers, authentication, SSE chat/fleet streams, and orchestration wiring.
  • pkg/launcher/ — composition roots for local code TUI, remote chat TUI, and server/daemon launch paths.
  • pkg/tui/, pkg/ui/ — Bubble Tea terminal clients and reusable terminal rendering.
  • pkg/tools/, pkg/browser/, pkg/codeintel/ — built-in tools, CDP browser automation, and source-code intelligence.
  • pkg/provider/, pkg/mcp/, pkg/skills/ — model providers, MCP integration, and skill loading.
  • pkg/config/ — configuration loading, defaults, and environment overrides.
  • pkg/store/ — storage interfaces and implementations/routing; tenant scope is a core invariant.
  • pkg/memory/, pkg/session/, pkg/fleet/, pkg/drill/, pkg/channels/ — major domain subsystems.
  • pkg/scheduler/ — scheduled-job registration and execution.
  • web/src/api/, web/src/components/chat/ — Studio transport contracts and chat rendering/interaction guidance.
  • pkg/sandbox/ — backend-neutral sandbox contracts plus Incus/Kubernetes/OpenShell implementations. Backend implementations must be concurrency-safe and lifecycle methods are intentionally idempotent.
  • ent/{platform,org,team,personal}/ — four persistence scopes. Only schema/*.go and generate.go are normally hand-edited; the remaining Ent files are generated.
  • web/src/ — Studio SPA. Entry points are main.tsx and App.tsx; api/ contains REST/SSE clients and components/ contains UI.
  • tests/e2e/, tests/e2eboot/, tests/scenarios/ — tagged E2E suites, shared bootstrap harness, and scenario catalogs/reporters.
  • docs/architecture/ — authoritative design documents. Update the relevant document when changing a documented protocol or invariant.
  • proto/, deploy/, docker/ — protocol definitions, deployment assets, and container images.

Read the full file on GitHub · 137 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. 3d ago First seen · 137 lines · 2,347 tokens per session scan A 52a7c449222a

Subscribe to this mod's changes

astonish AGENTS.md is an instructions file published in the GitHub repository SAP/astonish (20 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,347 tokens to every session, about $0.0117 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.

Related

Other instructions, from other repositories

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

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

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,182 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,345 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

next.js 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