Borrowing it
Nothing to install: this file belongs to iabhisekbosepm/codex-god-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iabhisekbosepm/codex-god-setup/main/.agents/skills/optimize/SKILL.mdgit clone --depth 1 https://github.com/iabhisekbosepm/codex-god-setupWrote 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/iabhisekbosepm/codex-god-setup/optimize)<a href="https://agentmods.dev/skills/iabhisekbosepm/codex-god-setup/optimize"><img src="https://agentmods.dev/badge/skills/iabhisekbosepm/codex-god-setup/optimize.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.00024 | $0.00191 |
| Opus 5 | $0.00012 | $0.00096 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
optimize 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 7d ago First seen · 17 lines · 24 tokens per session scan A c5669e26c079
optimize is a skill published in the GitHub repository iabhisekbosepm/codex-god-setup (1 stars, last pushed 5mo ago), with no licence file. It adds 24 tokens to every session and 191 once invoked, about $0.0001 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
systematic-debugging
A four-phase method for investigating software bugs and test failures before changing code. It focuses on finding and confirming the underlying cause.
bensz-collect-bugs
A process for recording bugs caused by defects in Bensz skills. It stores a structured local report and can publish one only when the user explicitly asks.
bugsnag-automation
Automate Bugsnag tasks via Rube MCP (Composio). Always search tools first for current schemas.
causal-explanation
Explain why or how an existing consequential behavior, design choice, regression, threshold, or tradeoff exists from current evidence and relevant history. Use for why, how, rationale, or postmortem questions and to explain an established root cause or regression finding; do not use to reproduce, diagnose, or…
bug-repro-plan
Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.
debugging-checklist
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.