Borrowing it
Nothing to install: this file belongs to sageox/ox. 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/sageox/ox/main/AGENTS.mdgit clone --depth 1 https://github.com/sageox/oxWrote 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/sageox/ox/agents-md)<a href="https://agentmods.dev/instructions/sageox/ox/agents-md"><img src="https://agentmods.dev/badge/instructions/sageox/ox/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.
<a href="https://agentmods.dev/instructions/sageox/ox/agents-md"><img src="https://agentmods.dev/badge/instructions/sageox/ox/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.04381 | $0.04381 |
| Opus 5.5 | $0.01752 | $0.01752 |
| Sonnet 5.5 | $0.00876 | $0.00876 |
| Haiku 4.5 | $0.00438 | $0.00438 |
Grade A, and why
ox 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 10d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run ox agent prime at session start to load SageOx team context — it's fine to read the user's request first.
Human attention is the scarcest resource
Human time is more expensive than compute. Before interrupting with a question, a PR for review, or a new issue, ask yourself: could I have resolved this without a human in the loop?
Default to independent resolution:
- Can you debug the issue yourself by reading code, running tests, checking logs, or using tools? Do that.
- Is the decision reversible? If yes, make the call and note the reasoning in a commit message. The human will tell you if they disagree.
- Do you have enough context from
CLAUDE.md, past sessions, or the codebase to decide? Decide. - Is this a genuinely novel tradeoff that sets precedent? That is worth interrupting for.
Prefer fewer, denser PRs over many small ones. A reviewer context-switching across four related PRs costs more than reviewing one larger coherent PR. Split only when the units of work are independent (different subsystems, different reviewers, different merge timing).
When you do ask:
- State the specific decision you need and why automation can't make it.
- Bundle related questions into one exchange rather than a stream of individual ones.
- Propose a default so the response can be "yes" / "no" / "do something else specific" rather than open-ended.
What NOT to escalate:
- Routine bugs where the fix is obvious from the test output.
- Style/lint issues.
- Choosing between two roughly-equivalent approaches when either would be fine.
- Asking permission for reversible operations (new branches, test runs, log analysis).
The cheapest review is the one that never has to happen because the code was right the first time. The next cheapest is a single coherent PR that tells a complete story. Optimize for those.
What is ox?
ox is agentic context infrastructure for software teams. It makes architectural decisions, team knowledge, and session history automatically available to AI coworkers — so every coding session starts with the full picture, not from zero.
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.
- 10d ago Changed · +19 tokens per session 013caf35bfa1
- 1mo ago Changed · +1 lines · +50 tokens per session c50581932d49
- 1mo ago Changed · +2 lines · +123 tokens per session 5f56d5e39c49
- 1mo ago Changed · +2 tokens per session 5a944168d06a
- 1mo ago Changed · -12 lines · -79 tokens per session 55aa5f0c6586
- 1mo ago First seen · 300 lines · 4,266 tokens per session scan A a652f09d62f3
ox AGENTS.md is an instructions file published in the GitHub repository sageox/ox (64 stars, last pushed today), licensed MIT. It adds 4,381 tokens to every session, about $0.0175 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.
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).
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).