codex-image-gen
/codex-image-gen
Generuje lub edytuje obraz przez narzędzie Codex CLI z innego agenta i diagnozuje zawieszone wywołania codex exec.
- Autor
- vickydotbat ↗
- Repozytorium
- vicky-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Generuje lub edytuje obraz przez narzędzie Codex CLI z innego agenta i diagnozuje zawieszone wywołania codex exec.
Wyzwalacze z opisu
Oryginalny opis (EN)
Generate or edit an image by driving the Codex CLI's built-in image tool from another agent. Use whenever a task says "use codex" for an image, art pass, meme, portrait or reference sheet, and whenever a `codex exec` call looks silent or stuck.
Jak działa
- Run
- Prove it is alive
- Failure modes
- Done
Podgląd SKILL.md
---
name: codex-image-gen
description: Generate or edit an image by driving the Codex CLI's built-in image tool from another agent. Use whenever a task says "use codex" for an image, art pass, meme, portrait or reference sheet, and whenever a `codex exec` call looks silent or stuck.
---
# Image generation through Codex
> _It's not dead, it's resting. Prove a quiet Codex is alive from its own files before you call it a hang._
`codex exec` is slow and quiet. One image takes about three minutes, and
stdout stays still for most of it. A still stdout is not a hang. Prove
liveness from Codex's own files before you wait, retry or report.
## Run
1. Write the prompt to a file in your scratch folder. Its first line tells
Codex: generate one image with the built-in image tool, save it to an
exact path relative to the working directory, write no other files, one
render, no edits afterwards. Codex edits its own render when it dislikes
it, and the edit wrecks it. Done when the file holds those instructions.
2. Attach references with `-i <path>` from where they live. Never copy them
into the workspace. Done when every reference is passed from its own location.
3. Run it in the background, capped, with stdin from the prompt file:
```sh
systemd-run --user --scope -p MemoryMax=4G -p MemorySwapMax=0 \
timeout 900 codex exec --skip-git-repo-check -s workspace-write \
-i <ref.png> < <scratch>/prompt.txt > <scratch>/out 2>&1; echo "exit=$?"
```
Stdin must be the prompt file. A `codex exec` with an open stdin and no
prompt waits forever for input. Done when the command is running and `exit=` is logged at the end; if it fails to start, report the error from `<scratch>/out`.
## Prove it is alive
Check these, newest first, with `${CLAUDE_PLUGIN_ROOT}/scripts/watch.sh '<check>'`, run by the Monitor tool:
- `pgrep -af "codex exec"` shows the process.
- `find ~/.codex/sessions -name 'rollout-*.jsonl' -mmin -5 | grep -q .`: this
run's rollout file still moves. Reading the image skill and the reference
images makes it large early. That is input, not output.
- `test -d ~/.codex/generated_images/<session id>`: the image landed. The
session id is the tail of the rollout file name.
- `test -e <target path>`.
Silent means none of these moved for five minutes while the process lives.
Then take the last 20 lines of the rollout file and look for a usage limit,
an approval prompt or an error before you stop it.
## Failure modes
- A usage limit prints in `<scratch>/out` with a reset time. Report the time.
Do not retry before it.
- A sandbox refusal to write the target: the image still sits in
`~/.codex/generated_images/<session id>/`. Copy it from there.
- `timeout` exit 124 with an image in `generated_images`: the render worked
and the save step died. Copy it. Without an image, rerun once.
- Run one render at a time against one quota.
## Done
Open the saved PNG and look at it before you report it. Done when the report names the path and the defects you see, or says "none seen".
Charter: C1 ([CHARTER.md](../../CHARTER.md)).
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · vickydotbat/vicky-skills | 100 | MIT |
| MrBogomips/skills | 100 | MIT |
| zazencodes/skills | 100 | MIT |
| techfreakworm/claude-soma | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki c75544982ebf (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100codex-cli
Deleguje zadania do OpenAI Codex CLI z innego środowiska agenta, na przykład Claude Code: sprawdza instalację, uruchamia polecenia codex exec, wznawia sesje, zbiera wyniki i obsługuje obrazy. - 95codex
Uruchamia Codex CLI przez codex exec i codex resume do analizy kodu, refaktoryzacji i automatycznych zmian w plikach. - 90codex
Uruchamia Codex CLI (codex exec, codex resume) do analizy kodu, refaktoryzacji i automatycznej edycji. - 100codex
Uruchamia Codex CLI (codex exec, codex resume) do analizy kodu, refaktoryzacji i automatycznej edycji. - 100codex
Uruchamia Codex CLI z innego agenta: zleca zadania przez codex exec, prowadzi równolegle kilku pracowników i zbiera raporty. - 90codex
Uruchamia Codex CLI, np. codex exec i codex resume, do analizy kodu, refaktoryzacji i zautomatyzowanych zmian.