sandstorm: Instructions file for Codex

AGENTS.md

sandstorm AGENTS.md is an instructions file for Codex, OpenCode from tomascupr/sandstorm. It costs 555 tokens per session, scanned A, original, MIT.

Repository guidelines for Sandstorm, a Python application with a FastAPI web server, command-line tool, sandbox orchestration, and Slack support.

In plain words
What is it for?
Use them to add modules and focused tests, run the development server, and verify code quality with the project's Python tooling.
Why use it?
They state where code belongs and which commands check installation, tests, formatting, linting, types, and imports.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 sandstorm AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tomascupr/sandstorm/agents-md"><img src="https://agentmods.dev/badge/instructions/tomascupr/sandstorm/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 555 This file is loaded in full into every session.
When invoked 555 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.00555 $0.00555
Opus 5.5 $0.00222 $0.00222
Sonnet 5.5 $0.00111 $0.00111
Haiku 4.5 $0.00056 $0.00056

Measured 1mo ago against content hash 8c9eb0bdd646, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sandstorm 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 1mo 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 · 29 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

Core application code lives in src/sandstorm/. Key modules include main.py for the FastAPI app, cli.py for the ds CLI, sandbox.py for E2B orchestration, and slack.py / slack_routes.py for Slack support. Deployment entrypoints live in api/, documentation in docs/, runnable configs in examples/, and test coverage in tests/. Keep new modules inside src/sandstorm/ and mirror them with focused tests such as tests/test_auth.py.

Build, Test, and Development Commands

Use Python 3.11+ and uv.

uv sync --extra dev              # install app + dev dependencies
ds serve --reload                # run the FastAPI server locally
uv run pytest tests/             # run the test suite
ruff check src/ tests/           # lint
ruff format --check src/ tests/  # formatting check
uv run pyright src/sandstorm/  # type check
uv run python -c "from sandstorm.main import app"  # smoke-test imports

If you use hooks locally, install them with uv run pre-commit install.

Coding Style & Naming Conventions

Follow Ruff defaults with the repo’s configured 99-character line length. Use 4-space indentation, snake_case for modules, functions, and variables, and PascalCase for classes. Keep FastAPI request/response models in models.py-style modules and prefer small, composable helpers over large route handlers. Run ruff check --fix src/ tests/ and ruff format src/ tests/ before opening a PR.

Testing Guidelines

Tests use pytest and live under tests/ with filenames matching test_<feature>.py. Prefer fixtures in tests/conftest.py and mock E2B or external API calls instead of hitting live services in unit tests. Some optional-path tests skip when Slack or OpenTelemetry extras are absent; install the relevant extras when working in those areas. For manual end-to-end work, use .env.example as the template and never commit real API keys.

Commit & Pull Request Guidelines

Recent history follows Conventional Commits: feat:, fix:, docs:, refactor:, test:, chore:. Keep commits scoped to one change. PRs should explain what changed, why it changed, and link the related issue (Fixes #123). Include screenshots or sample CLI/API output when changing user-facing behavior such as Slack flows, dashboard HTML, or streamed responses.

Read the full file on GitHub · 29 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. 1mo ago First seen · 29 lines · 555 tokens per session scan A 8c9eb0bdd646

Subscribe to this mod's changes

sandstorm AGENTS.md is an instructions file published in the GitHub repository tomascupr/sandstorm (448 stars, last pushed 6mo ago), licensed MIT. It adds 555 tokens to every session, about $0.0022 per session on Opus 5.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 · 9,649 tokens

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,549 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens