Skills/Glama/codex-img

codex-img@1.1.0

VERIFIED· startup only

Publisher claims: "Enables any MCP-compatible agent to generate and edit images using an existing Codex/ChatGPT subscription, exposing image generation and editing as tool calls." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher xurunxin · publishing for 2 daysInstalls 0Last detonated 39 h ago
$npx skills add codex-img
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials
Needs
OPENAI_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code; at startup it asked for OPENAI_API_KEY
Where it talks to
no vendor host named in the codeAlso chatgpt.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed (it asks for OPENAI_API_KEY); the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 40 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20sprocessrelaunched with a decoy OPENAI_API_KEY (tagged; nothing real)
40sclaimedstartup only: exited before answering, asking for OPENAI_API_KEY (a decoy value was refused)
40sprocessscript backend runs setup only
40sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandsrc/credentials.mjs:61 · File permission modification command — agent changes file ownership/permissions// chmod is a no-op on Windows and may fail on exotic filesystems.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File type combined with upload actionsrc/cli.mjs:149 · File type combined with upload action — agent may exfiltrate local data filesconsole.log(`bg: ${result.background ?? '?'} format: ${result.outputFormat ?? '?'}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈35 tok
1 file · 25 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.