OGX is an open-source API server for building AI applications, offering OpenAI-compatible interfaces while allowing applications to use different models and infrastructure. It is used by developers who want chat, embeddings, agent orchestration, tool calling, file search, and related services behind a common API.
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/ogx-ai/ogx/claude-mdgit clone --depth 1 https://github.com/ogx-ai/ogxWrote 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/ogx-ai/ogx/claude-md)<a href="https://agentmods.dev/instructions/ogx-ai/ogx/claude-md"><img src="https://agentmods.dev/badge/instructions/ogx-ai/ogx/claude-md.svg" alt="Measured on agentmods" 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.00562 | $0.00562 |
| Opus 5 | $0.00281 | $0.00281 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
ogx CLAUDE.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 6d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
See @AGENTS.md for guidelines on working with this codebase.
Design Context
Users
Backend engineers, application developers, and platform teams evaluating or adopting OGX for production AI workloads. They arrive from GitHub, blog posts, or search. They already use OpenAI/Anthropic SDKs and want to know: can I point my existing code at this server and have it just work? They are practical, time-constrained, and skeptical of marketing fluff. They read docs in dark terminals, IDEs, and browser tabs at all hours.
Brand Personality
Powerful, flexible, production-grade. Not flashy. Not cute. Not corporate. The kind of project where the README is better than most companies' entire docs site. Speaks in code examples, not marketing copy. Respects the developer's time above all else.
Three words: capable, direct, trustworthy.
Aesthetic Direction
- Tone: Technical confidence without pretension. Think: well-organized CLI output, a clean terminal, a tool that does exactly what it says.
- Theme: Dark mode default, both supported. Dark should feel like a refined terminal environment, not "glowing neon AI dashboard." Light should feel like clean paper, not washed-out gray.
- Anti-references: Purple-to-blue gradients, animated gradient text, icon-in-colored-circle card grids, "Works with 20+ providers!" vanity stats, marquee scrolling logos, decorative mesh backgrounds. All of these are present on the current site and should be replaced.
- Color: Move away from purple as primary. The logo uses a deep navy-to-teal gradient. The palette should feel grounded, not synthetic. Consider warm neutrals or muted earth tones as an alternative to the current purple/teal AI palette.
- Typography: Current fonts (Space Grotesk, Inter) are on the overused list. Find something with more character that still reads as technical and trustworthy.
Design Principles
- Show, don't decorate. Every visual element must communicate information. No decorative gradients, glows, or animations that exist for "wow factor."
- Code is the hero. The most important thing on the landing page is a working code example. Make it prominent, readable, and real.
- Earn trust through clarity. Clean structure, consistent spacing, and direct language signal competence better than any visual flourish.
- Respect the scroll. Every section must justify its existence. If it doesn't answer a question the developer has, cut it.
- No AI slop. If a pattern appears on 50 AI-generated landing pages, it doesn't belong here. When in doubt, do less.
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.
- 6d ago First seen · 30 lines · 562 tokens per session scan A c4ba0eb19fe0
ogx CLAUDE.md is an instructions file published in the GitHub repository ogx-ai/ogx (8,424 stars, last pushed yesterday), licensed MIT. It adds 562 tokens to every session, about $0.0028 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
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).
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.
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.
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.
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.
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).