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/ffaheem88/codexconnector/claude-mdgit clone --depth 1 https://github.com/ffaheem88/CodexConnectorWrote 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/ffaheem88/codexconnector/claude-md)<a href="https://agentmods.dev/instructions/ffaheem88/codexconnector/claude-md"><img src="https://agentmods.dev/badge/instructions/ffaheem88/codexconnector/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 | $0.01166 | $0.01166 |
| Opus 5 | $0.00583 | $0.00583 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
CodexConnector 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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
CodexConnector Workflow
CodexConnector has two actions: review (review code changes) and plan (get feedback on a plan before implementing it).
1. Code Review Workflow
After completing any code changes (features, bug fixes, refactors), you MUST run the Codex review process before considering the task done.
Process
-
Run the review after making changes:
codex-review "Review the changes I just made for bugs, edge cases, and improvements"If the project spans multiple repos in the same parent directory, review them all:
codex-review -d /path/to/parent-folder "Review all changes across repos" -
Analyze the feedback from Codex and identify:
- High priority issues (bugs, crashes, security issues)
- Medium priority issues (edge cases, error handling)
- Low priority issues (style, naming, best practices)
-
Fix the issues starting with high priority, then medium, then low.
-
Re-run the review after fixes:
codex-review "Verify the fixes address the previous issues" -
Repeat steps 2-4 until Codex reports no significant issues remaining.
When to Stop
The review loop is complete when:
- No High or Medium priority issues remain
- Codex confirms the code is satisfactory
- Only optional/stylistic suggestions remain (which can be noted but not necessarily fixed)
2. Plan Review Workflow
Before implementing a bug fix or a new module, you SHOULD run the Codex plan review to get feedback on your approach.
When to Use
- Planning a bug fix and want a second opinion on the approach
- Designing a new module or feature and want architectural feedback
- Evaluating whether an implementation plan accounts for edge cases
- Checking if a proposed change will conflict with existing code
Process
- Write the plan — either as a file or describe it inline:
# From a plan file codex-review -a plan -f plan.md # Inline description codex-review -a plan "Fix the race condition in the worker pool by adding a mutex around the shared counter and draining the channel before shutdown" # Both: plan file with extra focus instructions codex-review -a plan -f plan.md "Focus on thread safety concerns"
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.
- 3d ago First seen · 161 lines · 1,166 tokens per session scan A 5c941335a7b4
CodexConnector CLAUDE.md is an instructions file published in the GitHub repository ffaheem88/CodexConnector (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,166 tokens to every session, about $0.0058 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 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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.