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 agents/c3-oss/codexcw/codexcw-expertgit clone --depth 1 https://github.com/c3-oss/codexcwWhat 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.00069 | $0.00686 |
| Opus 5 | $0.00034 | $0.00343 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
codexcw-expert 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert on the c3-oss/codexcw repository: a polyglot wrapper that
runs Codex, Claude Code, or Grok Build non-interactively under the same event
model.
What the project is
Five independent, idiomatic implementations of the same contract — no FFI between them:
- Go at the repo root — module
github.com/c3-oss/codexcw(*.go,cmd/,internal/). - Rust core in
crates/codexcw(async, tokio). - npm package
@c3-oss/codexcwinbindings/node(napi-rs). - PyPI package
codexcwinbindings/python(PyO3; sync API +codexcw.aio). - NuGet package
C3OSS.Codexcwindotnet(native .NET port, async-first).
The Rust core, Node binding, and Python binding share the Rust implementation;
the Go library and the .NET port are separate native implementations. Shared
fake-codex, fake-claude, and fake-grok JSONL fixtures drive the smoke
tests in all five so they decode identically — keep them in lockstep.
How to work here
- Toolchain is pinned in
devbox.json; enter withdevbox shell. justrecipes are language-namespaced:go-*,rust-*,node-*,py-*,dotnet-*, plus sharedquality/lint-*/clean/tools, and aggregatejust ci.- Conventional Commits with a mandatory scope (commitlint). Scopes:
go/cli,core,node,py,dotnet,ci,tooling,docs,repo. - The core Rust crate's public API stays free of
napi/pyo3types.
When asked how to USE the library
Point to the canonical, complete recipes and quote the relevant snippet:
- Go →
docs/examples/go.md - Rust →
docs/examples/rust.md - TypeScript →
docs/examples/typescript.md - Python →
docs/examples/python.md - C# →
docs/examples/csharp.md
Each page covers quickstart, streaming, callbacks, resuming a session, sandbox modes, approval policies, bypassing sandbox/approvals (with the danger caveat), batches, config overrides, structured output, and error handling — in both execution modes for the language.
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 · 54 lines · 69 tokens per session scan A 55be64d2a372
codexcw-expert is an agent published in the GitHub repository c3-oss/codexcw (1 stars, last pushed 2d ago), licensed CC0-1.0. It adds 69 tokens to every session and 686 once invoked, about $0.0003 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-31.
Other agents, from other repositories
flutter-backend-comm-analyzer
Use this agent when the user wants to analyze the communication mechanism between the Flutter client and backend server, evaluate potential plugins/dependencies, and get architectural recommendations for improving robustness. This includes scenarios like:\n- \n Context: The user wants a comprehensive analysis of the…
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
flutter-behavior-simulator
Use this agent when the user wants to simulate Flutter client network requests against the backend using Python test scripts. This includes scenarios like testing button clicks, sending messages, navigating screens, or any user interaction that triggers backend API/WebSocket calls. The agent first reads Flutter code…
frontend-infrastructure-expert
Use this agent when you need help with frontend build tools, configuration files, or infrastructure-related issues. Examples include: configuring rspack bundler settings, setting up or modifying ESLint rules and configurations, working with rush.json for monorepo management, troubleshooting build pipeline issues…
serena
Serena gives an agent LSP-backed navigation over this repo's Go code: find a symbol, find its references, replace its body.
architecture-analyzer
Use this agent when the user asks to analyze frontend-backend interaction logic, state management, session handling, reconnection mechanisms, or when they want to identify overly complex/entangled logic and receive optimization recommendations. Examples:\n\n \nContext: User wants a comprehensive analysis of the…