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/elara-labs/code-context-engine/codexgit clone --depth 1 https://github.com/elara-labs/code-context-engineWhat 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.00012 | $0.00769 |
| Opus 5 | $0.00006 | $0.00385 |
| Sonnet 5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade B, and why
codex scanned grade B with 1 finding 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.codex/config.toml | grep cce How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex CLI uses a global configuration file rather than per-project MCP config. CCE registers itself in the user-level config with a project-specific section.
Quick setup
cce init --agent codex
Or let CCE auto-detect (if ~/.codex/ exists or the VS Code OpenAI extension is installed):
cce init
Files created
~/.codex/config.toml
Codex CLI reads MCP servers from this single user-global file. CCE adds one section per project, keyed by a slug derived from the project's absolute path:
[mcp_servers.cce-my-project-a3f2b1]
command = "cce"
args = ["serve", "--project-dir", "/path/to/your/project"]
Multiple projects coexist in the same file. Each gets a unique section name (cce-<basename>-<hash>) so two projects named "api" in different directories won't collide.
AGENTS.md
Contains instructions for Codex to use context_search for code exploration. The CCE block is wrapped in markers so your own content is preserved during upgrades.
Important notes
- Codex CLI does not support per-project
.mcp.jsonfiles. The global~/.codex/config.tomlis the only location for MCP server registration. - Running
cce uninstallremoves only the section for the current project. - If you're using Codex via the VS Code extension (not the CLI), CCE detects it by looking for
openai.*directories under~/.vscode/extensions/.
Verify it's working
- After
cce init, start a new Codex session in your project directory - Ask a code question:
How does error handling work in this project?
- Check that Codex calls
context_searchin the tool output - Verify savings:
cce savings
Cross-agent memory
Decisions recorded during Claude Code sessions (record_decision) are stored in the project's memory.db and shared across all agents. If you switch between Claude Code and Codex on the same project, session_recall returns decisions from both.
Troubleshooting
"cce: command not found" in Codex
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.
- yesterday First seen · 90 lines · 12 tokens per session scan B c70c0ae984b8
codex is an agent published in the GitHub repository elara-labs/code-context-engine (407 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 769 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
nopua-mentor-ja
Agent Team メンター役 — 他のチームメイトの実行状況を観察し、恐怖ではなく知恵で導く。行き詰まり、放棄、受け身に陥ったときは道徳経の知恵で啓発。5人以上のチーム推奨。.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.