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 commands/mturac/everything-openai-codex/auto-updategit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/commands/mturac/everything-openai-codex/auto-update)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/auto-update"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/auto-update.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.1 | $0.00013 | $0.00511 |
| Opus 5 | $0.00006 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
auto-update 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.
This is a copy
100% identical to auto-update — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Auto Update
Update ecc from its upstream repo and regenerate the current context's managed install using the original install-state request.
Usage
# Preview the update without mutating anything
ecc_ROOT="${CODEX_PLUGIN_ROOT:-$(node -e "var r=(()=>{var e=process.env.CODEX_PLUGIN_ROOT;if(e&&e.trim())return e.trim();var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.codex'),q=p.join('scripts','lib','utils.js');if(f.existsSync(p.join(d,q)))return d;for(var s of [['eoc'],['eoc@eoc'],['marketplace','eoc'],['ecc'],['ecc@ecc'],['marketplace','ecc'],['Everything OpenAI Codex'],['Everything OpenAI Codex@Everything OpenAI Codex'],['marketplace','Everything OpenAI Codex']]){var l=p.join(d,'plugins',...s);if(f.existsSync(p.join(l,q)))return l}try{for(var g of ['eoc','ecc','Everything OpenAI Codex']){var b=p.join(d,'plugins','cache',g);for(var o of f.readdirSync(b,{withFileTypes:true})){if(!o.isDirectory())continue;for(var v of f.readdirSync(p.join(b,o.name),{withFileTypes:true})){if(!v.isDirectory())continue;var c=p.join(b,o.name,v.name);if(f.existsSync(p.join(c,q)))return c}}}}catch(x){}return d})();console.log(r)")}"
node "$ecc_ROOT/scripts/auto-update.js" --dry-run
# Update only Cursor-managed files in the current project
node "$ecc_ROOT/scripts/auto-update.js" --target cursor
# Override the ecc repo root explicitly
node "$ecc_ROOT/scripts/auto-update.js" --repo-root /path/to/Everything OpenAI Codex
Notes
- This command uses the recorded install-state request and reruns
install-apply.jsafter pulling the latest repo changes. - Reinstall is intentional: it handles upstream renames and deletions that
repair.jscannot safely reconstruct from stale operations alone. - Use
--dry-runfirst if you want to see the reconstructed reinstall plan before mutating anything.
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 · 29 lines · 13 tokens per session scan A 7f125b1ed506
auto-update is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 12d ago), licensed MIT. It adds 13 tokens to every session and 511 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to auto-update, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
patterns
Show the full agentpatterns report — success rate, approach→outcome correlation, top patterns.