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.
npx agentmods add instructions/apache/texera/agents-mdgit clone --depth 1 https://github.com/apache/texeraWhat 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 | $0.03084 | $0.03084 |
| Opus 5 | $0.01542 | $0.01542 |
| Sonnet 5 | $0.00617 | $0.00617 |
| Haiku 4.5 | $0.00308 | $0.00308 |
Grade A, and why
texera 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Architecture Map
Apache Texera: Scala/sbt backend services + the Amber workflow execution
engine, an Angular UI, and the agent service. JVM modules wired in
build.sbt.
| Area | Path | Detail |
|---|---|---|
| Workflow execution engine (Amber) | amber/ |
amber/README.md |
| Backend services | config-service/, access-control-service/, file-service/, computing-unit-managing-service/, workflow-compiling-service/, notebook-migration-service/ |
build.sbt |
| Shared Scala libs | common/ (auth, config, dao, util, workflow-core, workflow-operator, pybuilder) |
build.sbt |
| Frontend (Angular) | frontend/ |
frontend/README.md |
| Agent service (Bun/TS, LLM agents) | agent-service/ |
agent-service/package.json |
| Pyright language service | pyright-language-service/ |
pyright-language-service/README.md |
| Deploy scripts / Dockerfiles | bin/ |
README / k8s / single-node |
| DDL, sbt plugins | sql/, project/ |
files therein |
Amber breakdown
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.
- 2d ago First seen · 263 lines · 3,084 tokens per session scan A ad116bcce3a0
texera AGENTS.md is an instructions file published in the GitHub repository apache/texera (276 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,084 tokens to every session, about $0.0154 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.
Other instructions, from other repositories
marimo AGENTS.md
Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.
marimo copilot-instructions.md
Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
marimo CLAUDE.md
Instructions for marimo-team/marimo, a project described as: A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
streamlit copilot-instructions.md
Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
swarms CLAUDE.md
Instructions for kyegomez/swarms, covering claude.md — swarms framework guide, installation & setup, any provider supported by litellm works, project layout and core primitive: agent.
zenml CLAUDE.md
Instructions for zenml-io/zenml, covering zenml claude code guidelines, project structure, use zenml docs via mcp, code style & quality standards and commenting policy — explain why, not what.