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/ecc-guidegit 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/ecc-guide)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/ecc-guide"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/ecc-guide.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.00023 | $0.00701 |
| Opus 5 | $0.00012 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
ecc-guide 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
94% identical to ecc-guide — 10 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ecc-guide
Use this command as a conversational map of Everything OpenAI Codex. It should help the user discover the right ecc surface for their task without dumping the entire README or stale catalog counts.
Usage
/ecc-guide
/ecc-guide setup
/ecc-guide skills
/ecc-guide commands
/ecc-guide hooks
/ecc-guide install
/ecc-guide find: <query>
/ecc-guide <feature-or-file-name>
Operating Rules
- Read current repository files before answering when the checkout is available.
- Prefer current filesystem/catalog data over hard-coded counts.
- Keep the first answer short, then offer specific drill-down paths.
- Link users to canonical files instead of copying long sections.
- Do not invent commands, skills, agents, or install profiles that are not present.
What To Inspect
Use these files as the canonical map:
README.mdfor install paths, reset/uninstall guidance, and high-level positioningAGENTS.mdfor contributor and project-structure guidanceagent.yamlfor exported agent and command surfacecommands/for maintained slash-command shimsskills/*/SKILL.mdfor reusable skill workflowsagents/*.mdfor delegated agent roleshooks/README.mdandhooks/hooks.jsonfor hook behaviormanifests/install-*.jsonfor selective install modules, components, and profilesscripts/ci/catalog.js --jsonfor live catalog counts when running inside ecc
Response Patterns
No Arguments
Give a compact menu:
- setup and install
- choosing skills
- command compatibility shims
- agents and delegation
- hooks and safety
- troubleshooting an install
- finding a specific feature
Then ask what they want to do next.
Topic Lookup
For topics like skills, commands, hooks, install, or agents:
- Summarize the current surface in 3-6 bullets.
- Point to the canonical directories/files.
- Suggest one or two commands that can verify the state.
- Avoid exhaustive lists unless the user asks for one.
Search Mode
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 · 94 lines · 23 tokens per session scan A 308aa278cbb8
ecc-guide is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to ecc-guide, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
teach
Hand-record a lesson into Memory Fabric (learning tier, high confidence) so it is recalled later.
quiz-result
Analyze quiz progress over time and the weak areas to study next, from a KMS scores log.
start-10-1.es
Lección 10-1: Configuración del entorno de desarrollo GAS!
start-11-1.es
Lección 11-1: Introducción a GitHub Actions!
start-12-4.en
Command "start-12-4.en" from minicoohei/ai-agent-camp, covering 🎓 lesson 12-4: automated report generation, 📍 what you'll do, 🎯 readiness check, 🚀 step 1: create task management database and 🚀 step 2: add sample tasks.
explain
Generate an interactive one-module explainer for a topic — Riko gathers code scope, Senku plans a 3-5 screen teaching arc, Speedwagon authors the HTML, assembler produces explain-out/index.html.