Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Image Gen Compare
v1.0.1Side-by-side comparison of paid vs local image generation models — DALL-E 3, FLUX.1-schnell, Gemini Imagen, and others. Generates images from the same prompt...
⭐ 0· 317·1 current·1 all-time
byNissan Dookeran@nissan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description (compare paid vs local image models) matches the included script: it calls OpenAI for DALL‑E and local libraries for FLUX/SDXL. However it hardcodes a Proton Drive path for outputs and expects to fetch secrets from 1Password—these are plausible but not obviously necessary to the stated purpose and are unusual choices (especially a single Proton Drive path baked into the script).
Instruction Scope
SKILL.md and the script instruct the agent to use network outbound calls (OpenAI API, HuggingFace model downloads), read/write files (workspace content plus a hardcoded Proton Drive path), and invoke the 1Password CLI via subprocess to retrieve keys. The instructions reference reading a local token file (~/.config/openclaw/.op-service-token) and running 'op read op://OpenClaw/OpenAI API Key/credential' — these expand scope to local credential stores and system CLI tools outside the stated domain of image generation.
Install Mechanism
No install spec (instruction-only) — lower risk because nothing is installed automatically. But the script imports requests, mflux, diffusers, torch, etc., and will require the user to pip-install large ML packages and model downloads from HuggingFace. Those downloads are expected for local models but can be large (~7–9GB).
Credentials
Declared required env vars are OPENAI_API_KEY and OP_SERVICE_ACCOUNT_TOKEN. OPENAI_API_KEY is proportionate for DALL‑E. OP_SERVICE_ACCOUNT_TOKEN is plausible for using the 1Password CLI, but the script does not actually read OP_SERVICE_ACCOUNT_TOKEN from the environment by default: it first checks OPENAI_API_KEY then attempts to read a token file (~/.config/openclaw/.op-service-token) and sets that into the subprocess env. The script also invokes the 'op' CLI, but 'op' is not declared as a required binary. Requiring a 1Password service token grants access to stored secrets—this is sensitive and should be justified and handled explicitly by the user.
Persistence & Privilege
The skill is not always:true and does not request persistent platform privileges. It writes outputs and a runs.json into workspace and may write into a Proton Drive folder if present; it invokes 'op' but does not modify other skills or global agent settings.
What to consider before installing
This skill does what it says (compare image generators), but take these precautions before installing or running it:
- Secrets: It needs your OPENAI_API_KEY. It also expects a 1Password service token (OP_SERVICE_ACCOUNT_TOKEN) / or a token file at ~/.config/openclaw/.op-service-token to run the 'op' CLI and fetch the OpenAI key. Providing a 1Password service token gives the script the ability to read stored secrets—only proceed if you trust the code and the exact 1Password item path (op://OpenClaw/OpenAI API Key/credential).
- Binaries and deps: The script calls the 'op' CLI but the skill metadata does not list 'op' as a required binary. Ensure 'op' is installed and reviewed before use. You will also need to install Python packages (requests, mflux, diffusers, torch, etc.) and expect large model downloads from HuggingFace (>7GB). Run in an environment with sufficient disk space and network policy you control.
- File writes: The script will save images and runs.json into workspace/content/images and—if a Proton Drive path exists—into a hardcoded Proton Drive directory. If you do not want artifacts copied to cloud‑synced folders, check or remove that hardcoded path in the script first.
- Audit before running: Because the script invokes subprocesses and accesses local credential stores, review the code yourself (or run it in an isolated VM/container) to confirm it only accesses the locations you expect. Consider setting OPENAI_API_KEY directly instead of giving the script access to your 1Password service account, or remove the 1Password fetch logic if you prefer.
If you are comfortable with those behaviors (network outbound, large downloads, local file writes, and optional 1Password access), the skill is coherent enough for use; if not, treat it as untrusted and do not provide sensitive tokens or run it on a production machine.Like a lobster shell, security has layers — review code before you run it.
latestvk970b1kwmmyysq229av6tfh0t583r0rw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🖼️ Clawdis
Binspython3
EnvOPENAI_API_KEY, OP_SERVICE_ACCOUNT_TOKEN
Primary envOPENAI_API_KEY
