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/bman654/clodex/claude-mdgit clone --depth 1 https://github.com/bman654/clodexWrote 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/bman654/clodex/claude-md)<a href="https://agentmods.dev/instructions/bman654/clodex/claude-md"><img src="https://agentmods.dev/badge/instructions/bman654/clodex/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.03470 | $0.03470 |
| Opus 5 | $0.01735 | $0.01735 |
| Sonnet 5 | $0.00694 | $0.00694 |
| Haiku 4.5 | $0.00347 | $0.00347 |
Grade B, and why
clodex CLAUDE.md 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 today.
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.
- **`~/.claude/settings.json` is never touched by clodex.** Launch config is env-var-only (plus How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for coding agents and maintainers working in this repo. Read this file in full; load the deeper documents below only when you touch the subsystem they cover.
clodex bridges Claude Code to non-Anthropic models — OpenAI API key (openai),
ChatGPT/Codex-plan OAuth (openai-oauth), or community-supported OpenCode Go (opencode-go).
Provider support tiers are documented in README. It is a trimmed fork of relay-ai (full commit
history preserved).
Prime directive. The translation, caching, auto-compaction, and OAuth-continuation code encodes real production failures that are not visible in the diff. Prefer surgical changes over restructuring.
Where everything lives
| Load this | When |
|---|---|
.claude/skills/pr-verification/SKILL.md |
Before the first git push of any change — the gate it must clear, and why pushing before your review reports costs more than it saves. Load it when you start preparing the change, not when you are about to open the PR. |
.claude/skills/pr-review/SKILL.md |
Reviewing someone else's PR: panels, proof techniques, verdicts, merging. |
.claude/docs/claude-code-internals.md |
Before asserting how Claude Code itself behaves, or re-deriving it. |
.claude/docs/patcher.md |
Changing clodex patch, patch transforms, or backups. |
.claude/docs/oauth-continuation.md |
Changing src/oauth/, head matching, upstream retries, WS diagnostics. |
.claude/docs/translation.md |
Changing sdk-adapter.ts, provider-factory.ts, openai-adapter.ts. |
.claude/docs/launch-and-wrapper.md |
Changing launch, bridge modes, env, server discovery, clodex-claude, outbound proxy. |
.claude/docs/registry-and-server.md |
Changing src/registry/, src/server/, model or alias resolution. |
CONTRIBUTING.md |
Outside contributors: how to scope a PR. |
RELEASING.md |
Maintainers: how a release is cut and staged. |
.agents is a committed symlink to .claude, so harnesses that look for .agents/ find the same
skills and docs.
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.
- today Changed · +6 lines · +110 tokens per session 4794d32e2e05
- 4d ago First seen · 221 lines · 3,360 tokens per session scan B 2795b118e869
clodex CLAUDE.md is an instructions file published in the GitHub repository bman654/clodex (50 stars, last pushed today), licensed MIT. It adds 3,470 tokens to every session, about $0.0174 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 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.