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/ucsahinn/codex-chef/codex-chef-operatornpx skills add ucsahinn/codex-chef --skill codex-chef-operatorgit clone --depth 1 https://github.com/ucsahinn/codex-chefWrote 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/ucsahinn/codex-chef/codex-chef-operator)<a href="https://agentmods.dev/skills/ucsahinn/codex-chef/codex-chef-operator"><img src="https://agentmods.dev/badge/skills/ucsahinn/codex-chef/codex-chef-operator.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.00055 | $0.00599 |
| Opus 5 | $0.00028 | $0.00300 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
codex-chef-operator 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Chef Operator
Use this skill when maintaining the Codex Chef repository or a derived local setup.
Reference Routing
Read references/repo-maintenance.md before broad setup, installer, README,
catalog, docs, verification, release-readiness, or public-repo changes. Keep
SKILL.md as the routing entry point and put detailed repo policy in that
reference.
Workflow
- Inspect current files before changing anything.
- Preserve security defaults:
- sandbox stays enabled
- approvals stay interactive
- authenticated connectors stay disabled until needed
- no secrets, sessions, memories, auth files, or local project paths are added to source
- Keep docs and templates aligned:
AGENTS.mdREADME.mdREADME.tr.mdtemplates/codex/AGENTS.mdtemplates/codex/config.windows.tomltemplates/codex/config.unix.tomldocs/how-to.mddocs/how-to.tr.mddocs/skills-and-agents.mddocs/skills-and-agents.tr.mddocs/mcp-catalog.mddocs/mcp-catalog.tr.mddocs/codex-flags.mddocs/codex-flags.tr.mddocs/public-readiness.mddocs/public-readiness.tr.mddocs/install.mddocs/install.tr.mddocs/security-model.md- every English operator doc in
docs/should have a matching.tr.mdpair - the six root README entry points should route readers honestly to the complete English and Turkish operator docs
- bundled local skills should stay reference-backed, zero-network unless their own script or workflow explicitly says otherwise, and validated by repo checks
- public README visuals under
assets/should stay purposeful, accessible, lightly animated with reduced-motion fallback, and public-safe
- Validate after edits:
npm run validatenpm run validate:plugin-skillsgit status --short- Gitleaks when available
- Do not commit, push, tag, release, deploy, publish, rotate credentials, or perform account-level changes unless the user explicitly approves the exact action.
What ships with it
2 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 · 71 lines · 55 tokens per session scan A a27e64e63bf6
codex-chef-operator is a skill published in the GitHub repository ucsahinn/codex-chef (6 stars, last pushed 17d ago), licensed MIT. It adds 55 tokens to every session and 599 once invoked, about $0.0003 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
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
map-wayfind
Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.