Borrowing it
Nothing to install: this file belongs to poteto/noodle. 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/poteto/noodle/main/.agents/skills/codex/SKILL.mdgit clone --depth 1 https://github.com/poteto/noodleWrote 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/poteto/noodle/codex)<a href="https://agentmods.dev/skills/poteto/noodle/codex"><img src="https://agentmods.dev/badge/skills/poteto/noodle/codex/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/poteto/noodle/codex"><img src="https://agentmods.dev/badge/skills/poteto/noodle/codex.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.00063 | $0.00892 |
| Opus 5.5 | $0.00025 | $0.00357 |
| Sonnet 5.5 | $0.00013 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
codex 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex
Profiles
- (no profile) — read-only analysis (no compilation, no tests)
--profile edit— local edits, build, or test (workspace-write, full-auto)--profile full— network or broad filesystem access (danger-full-access, full-auto)
Use --profile edit whenever the task involves go test, go build, or any command that writes build artifacts. The default read-only sandbox blocks all writes including compiler temp dirs.
For complex tasks, add --config model_reasoning_effort="xhigh".
Model Selection
Default to the project model in .codex/config.toml (gpt-5.4).
Use --model gpt-5.3-codex-spark for speed-first interactive work:
- tight back-and-forth iteration
- quick bug fixes and targeted edits
- small-to-medium refactors or UI tweaks
- rapid prototyping where frequent redirect/interrupt is expected
Stay on default gpt-5.4 for depth-first work:
- long autonomous runs
- broad multi-file changes with heavy reasoning
- test-heavy or verification-heavy tasks
- higher correctness/risk surfaces where deeper reasoning is worth the extra latency
If the user explicitly requests a model, follow the user's request.
Commands
Project defaults in .codex/config.toml. Always include --skip-git-repo-check and 2>/dev/null. Only override model when the user explicitly requests it, or when the task clearly fits the Spark speed-first criteria above.
| Use case | Command |
|---|---|
| Read-only analysis | codex exec --skip-git-repo-check -o "$CODEX_OUT" "prompt" 2>/dev/null |
| Speed-first interactive loop (Spark) | add --model gpt-5.3-codex-spark |
| Apply local edits | add --profile edit |
| Network / broad access | add --profile full |
| Resume session | echo "prompt" | codex exec --skip-git-repo-check -o "$CODEX_OUT" resume --last 2>/dev/null |
Create a temp file for output before running: CODEX_OUT=$(mktemp /tmp/codex-out.XXXXXX). Read the result from $CODEX_OUT after completion.
Run with Bash run_in_background: true. Monitor via TaskOutput with block: true, timeout: 600000 — do NOT use sleep commands to poll. Read the -o file for the final answer.
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.
- 1mo ago First seen · 76 lines · 63 tokens per session scan A 277cd1242925
codex is a skill published in the GitHub repository poteto/noodle (529 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 892 once invoked, about $0.0003 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…