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/skills/openspec-context-docs/SKILL.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/skills/soju06/codex-lb/openspec-context-docs)<a href="https://agentmods.dev/skills/soju06/codex-lb/openspec-context-docs"><img src="https://agentmods.dev/badge/skills/soju06/codex-lb/openspec-context-docs/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/skills/soju06/codex-lb/openspec-context-docs"><img src="https://agentmods.dev/badge/skills/soju06/codex-lb/openspec-context-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00446 |
| Opus 5.5 | $0.00021 | $0.00178 |
| Sonnet 5.5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
openspec-context-docs 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.
What it actually says
OpenSpec Context Docs
When to use
- Writing or updating OpenSpec documentation (specs, onboarding, guide, change artifacts).
- A spec is complete but readers lack background, rationale, examples, or operational notes.
- You need to preserve rich context without weakening SSOT.
Core rule: two-layer docs
spec.md= normative, testable requirements (SHALL/MUST + scenarios).- Context docs = narrative and operational detail that helps humans understand and apply the spec.
Locations
- Main specs:
openspec/specs/<capability>/spec.md(requirements)openspec/specs/<capability>/context.md(preferred)
- Optional split (if context grows):
overview.md,rationale.md,examples.md,ops.mdinside the same capability folder.
- Change-level notes (working context):
openspec/changes/<change>/context.mdornotes.md
Detail prompts (add depth without forcing a template)
Include at least 4 of these in context docs:
- Purpose / scope / non-goals
- Decision rationale + alternatives considered
- Constraints (security, performance, policy)
- Failure modes / edge cases
- Example request/response, data shape, or user flow
- Operational notes (rollout, monitoring, runbooks)
- Links to related specs/contracts
Sync rule
- After implementation/verification, promote stable context from change notes into the main context docs.
- Do not duplicate normative requirements in context docs; link back to
spec.md. - Never create or update a
docs/directory; keep everything underopenspec/.
Prompt snippet
"Keep spec.md strictly for requirements. Add/update context.md with purpose, decisions, constraints, failure modes, and at least one concrete example."
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 First seen · 49 lines · 52 tokens per session scan A d00a9d2b551b
openspec-context-docs is a skill published in the GitHub repository Soju06/codex-lb (3,382 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 446 once invoked, about $0.0002 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 skills, from other repositories
meeting-facilitate
A process for running structured meetings between multiple software agents. It covers choosing a meeting format, bringing in participants, managing discussion rounds, checking attendance, and producing a summary.
os-workflow
A workflow guide for sending work from an AI Team OS project back into its task records. It explains how a lead agent and workflow agents record progress and important results.
os-channel
A message channel that lets separate AI sessions, such as Claude Code and Codex, send messages, check unread messages, and in some cases be prompted to check them.
meeting-participate
A meeting procedure for AI Team OS agents working together in structured discussion rounds. It covers reading earlier messages and sending a signed contribution.
os-release
A release checklist for publishing a new version of AI Team OS. It covers checks, synchronized version updates, bilingual release notes, builds, commits, tags, repository pushes, and GitHub release records.
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs, Pydantic models, dependencies, streaming responses including Server-Sent Events (SSE), and serving frontend apps. Keeps FastAPI code clean and up to date with the latest features and patterns.