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 skills/yankieldbc2/codex-skills-library/codex-efficiency-benchmarknpx skills add YankielDBC2/codex-skills-library --skill codex-efficiency-benchmarkgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/codex-efficiency-benchmark)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/codex-efficiency-benchmark"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/codex-efficiency-benchmark.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.00037 | $0.00474 |
| Opus 5 | $0.00018 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
codex-efficiency-benchmark 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.
What it actually says
Codex Efficiency Benchmark
Goal
Measure whether Codex skills and project process guidance reduce token waste, elapsed time, file scanning, validation churn, and dead ends compared with a minimal baseline.
When to use
Use this skill when you need to compare "with skills" versus "without skills" on a real task, bootstrap, refactor, or recovery workflow.
When not to use
Do not use this skill for unrelated implementation tasks that do not need a control vs treatment comparison.
Inputs
- Project context files such as
AGENTS.md,docs/CODEBASE_INDEX.md, anddocs/PROJECT_CONTEXT.md. - A baseline scenario that uses minimal guidance.
- A treatment scenario that uses the relevant skills, docs, and process rules.
- A run log in
templates/project/EFFICIENCY_RUN.jsonformat or equivalent project-local JSON.
Workflow
- Define the scenario, goal, and success criteria.
- Run or reconstruct the baseline variant with the smallest safe context.
- Run the treatment variant with the relevant skills and repo rules.
- Record start and end timestamps, files read, files changed, commands run, validations, rework loops, dead ends, and token usage if available.
- Compare control and treatment with
npm run compare:efficiencyor the equivalent script. - Explain which metrics improved, which regressed, and why.
- Capture the decision in
docs/CODEX_STATE.md,docs/PLANS.md, or project-local state files.
Quality bar
- The comparison must be the same task, same repo state, and same acceptance criteria.
- Exact token usage is preferred when available from the goal metadata; otherwise record an explicit estimate and source.
- The result must separate real improvements from noise caused by different task scope or validation depth.
Validation
Run the relevant validation for the task plus the benchmark comparison command.
Final response
Report the control/treatment setup, metrics, deltas, confidence limits, and next experiment.
What ships with it
4 files 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.
- 3d ago First seen · 53 lines · 37 tokens per session scan A 24a3db7731af
codex-efficiency-benchmark is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 474 once invoked, about $0.0002 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 skills, from other repositories
sql-reporting
Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
verify-security
安全校验关卡。自动扫描代码安全漏洞，检测危险模式，确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变更、攻防任务、重构完成时自动触发。.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.