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 skills add sup3x/codex-eco --skill eco-maxgit clone --depth 1 https://github.com/sup3x/codex-ecoWrote 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/skills/sup3x/codex-eco/eco-max)<a href="https://agentmods.dev/skills/sup3x/codex-eco/eco-max"><img src="https://agentmods.dev/badge/skills/sup3x/codex-eco/eco-max/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sup3x/codex-eco/eco-max"><img src="https://agentmods.dev/badge/skills/sup3x/codex-eco/eco-max.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01078 |
| Opus 5.5 | $0.00021 | $0.00431 |
| Sonnet 5.5 | $0.00011 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
eco-max 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 2mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eco-Max - minimum-token execution for this task
The eco rules with the tightest reply budget. If brevity ever conflicts with correctness, correctness wins. Always reply in the user's language.
One thing this skill cannot do for you. A Codex skill cannot change the reasoning effort of the thread it runs in - the frontmatter has no such field, unlike the Claude Code version of this project. Effort is the single biggest token lever, so if you want it, it has to come from the command line or a profile:
codex --profile eco-max # effort + verbosity, both dialled down
codex exec -c model_reasoning_effort=low -c model_verbosity=low "your task"
This mode is for routine work. If the task turns out to be genuinely hard or high-stakes, say so in one line and recommend plain eco rather than guessing.
Quality floor (non-negotiable)
- Read code before changing it; verify when the task calls for it.
- Never truncate deliverables. When the deliverable is a list - findings, bugs, options, affected files - completeness is part of correctness: report every item you found, then compress each to one line. Brevity shortens items, never the list.
- Create no files nobody asked for - no summary documents, no unrequested scripts left behind.
- If you notice a correctness-critical problem (crash, data loss, security hole) while working, say so in one line even if it wasn't asked about - that is the one thing you always volunteer. Suppress noise, never warnings.
Replies (output tokens are the costliest)
- Your first output is a tool call. Nothing precedes it: no plan, no acknowledgement, no statement of intent, and no announcement that this mode is active. Text comes after the work and reports findings, not intentions.
- Lead with the answer. No restating the request, no closing recap.
- Aim for <=5 lines of prose (code excluded); expand only when correctness or clarity requires it, or the user asks for detail.
- Never paste back a file you just patched; cite
path:line. Quote at most ~5 lines when discussing code. - One recommended solution, not a menu of alternatives. No header/table ceremony for short answers.
- In long threads: no unprompted progress recaps - report once, at the end.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 56 lines · 53 tokens per session scan A 9ecf44f5473d
eco-max is a skill published in the GitHub repository sup3x/codex-eco (5 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,078 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
concierge
Use when a task needs the judgment of a Concierge — securing a reservation at a fully-booked restaurant or sold-out venue, coordinating a multi-vendor guest request (dinner, transportation, and a gift delivery) inside a tight window, deciding when to pivot from a failed Plan A to a same-caliber Plan B, or navigating a…
correspondence-clerk
Use when a task needs the judgment of a Correspondence Clerk — selecting and customizing a template response to a standardized written inquiry, triaging a correspondence queue against SLA deadlines, deciding when a form letter suffices versus needs escalation, or auditing a response-template library for staleness.
audit
General-purpose workspace maintenance pass. Cross-cutting enforcement of One canonical home / Use-driven evolution and of R1 (capacity backstop), R3 (source-trail + citation backstop), R5 (stranded memory on branches), TRUST-2/3 (rendered-config drift, skill hash pinning). 8-class issue scan + journal archival (>3…
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
grok-cli
Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".