codex-lb is a proxy and load balancer that combines multiple ChatGPT accounts behind one service, tracks their usage, manages API keys, and provides a dashboard. It is for people using Codex CLI, OpenCode, or other OpenAI-compatible clients who need account pooling and usage monitoring. Catalogue add-ons can operate it through its compatible endpoints.
Borrowing it
Nothing to install: this file belongs to Soju06/codex-lb. 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/Soju06/codex-lb/main/AGENTS.mdgit clone --depth 1 https://github.com/Soju06/codex-lbWrote 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/soju06/codex-lb/agents-md)<a href="https://agentmods.dev/instructions/soju06/codex-lb/agents-md"><img src="https://agentmods.dev/badge/instructions/soju06/codex-lb/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/soju06/codex-lb/agents-md"><img src="https://agentmods.dev/badge/instructions/soju06/codex-lb/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.01974 | $0.01974 |
| Opus 5.5 | $0.00790 | $0.00790 |
| Sonnet 5.5 | $0.00395 | $0.00395 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
codex-lb 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Environment
- Python:
>=3.13viauv(uv sync --frozen; interpreter at.venv/bin/python) - GitHub auth for git/API is available via env vars:
GITHUB_USER,GITHUB_TOKEN(PAT). Do not hardcode or commit tokens. - For authenticated git over HTTPS in automation, use:
https://x-access-token:${GITHUB_TOKEN}@github.com/<owner>/<repo>.git
Code Conventions
The /project-conventions skill is auto-activated on code edits (PreToolUse guard).
| Convention | Location | When |
|---|---|---|
| Code Conventions (Full) | /project-conventions skill |
On code edit (auto-enforced) |
| Git Workflow | .agents/conventions/git-workflow.md |
Commit / PR |
Workflow (OpenSpec-first)
This repo uses OpenSpec as the primary workflow and SSOT for change-driven development.
How to work (default)
- Find the relevant spec(s) in
openspec/specs/**and treat them as source-of-truth. - If the work changes behavior, requirements, contracts, or schema: create an OpenSpec change in
openspec/changes/**first (proposal -> tasks). - Implement the tasks; keep code + specs in sync (update
spec.mdas needed). - Validate specs locally:
openspec validate --specs - When done: verify + archive the change (do not archive unverified changes).
Source of Truth
- Specs/Design/Tasks (SSOT):
openspec/- Active changes:
openspec/changes/<change>/ - Main specs:
openspec/specs/<capability>/spec.md - Archived changes:
openspec/changes/archive/YYYY-MM-DD-<change>/
- Active changes:
Documentation & Release Notes
- OpenSpec is the SSOT for feature/behavior documentation. User-facing rendering lives under
docs/(the published docs pages), and each spec-governed page MUST link back to the owningopenspec/specs/<capability>/entry. Do not createdocs/content that has no OpenSpec counterpart, and do not add feature docs as new README sections. Keep normative requirements inopenspec/specs/<capability>/spec.mdand free-form rationale in the capability'scontext.md(or change-level context underopenspec/changes/<change>/context.md). - Do not edit
CHANGELOG.mddirectly. Leave changelog updates to the release process; record change notes in OpenSpec artifacts instead.
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.
- 1mo ago Changed · +3 lines · +60 tokens per session f9caba7c3dbe
- 1mo ago Changed · +8 tokens per session bfd1c539f759
- 1mo ago First seen · 140 lines · 1,906 tokens per session scan A 5d64b99feea3
codex-lb AGENTS.md is an instructions file published in the GitHub repository Soju06/codex-lb (3,382 stars, last pushed 2d ago), licensed MIT. It adds 1,974 tokens to every session, about $0.0079 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.
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).
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.