Agent-first Marketing Image Generation
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears to do what it says—generate marketing images through Rynjer—but live use sends prompts to Rynjer and can spend Rynjer credits using an access token.
This looks coherent for a Rynjer image-generation workflow. Before installing or enabling live mode, confirm you trust the Rynjer account integration, use a limited-scope token, run cost estimates before generation, and avoid sending confidential prompt content.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Using generate_image in live mode can spend Rynjer credits or use paid API access.
The main generation tool is explicitly a paid API action. This is expected for an image-generation skill, but users should understand an agent can consume credits when live mode is enabled.
Pricing boundary: - rewrite: free - estimate: free - generate: paid via Rynjer credits or API access
Run estimate_image_cost first, keep generation counts small, and only enable live credentials when you intend the agent to generate images.
Anyone with the token may be able to use the linked Rynjer account capabilities and credits allowed by its scopes.
The live flow uses a Rynjer agent/API key as bearer authentication for generation endpoints. This is purpose-aligned, but it is still account authority that should be scoped and protected.
returned `ryn_agent_v1_...` key is then used directly as Bearer auth for generation endpoints
Use a minimal-scope Rynjer agent key, avoid sharing it, monitor credit usage, and revoke the key when it is no longer needed.
Prompt text and generation metadata may leave the local agent environment and be processed by Rynjer.
Live generation sends the user's prompt and generation parameters to the external Rynjer service. This is central to the skill, but prompts may contain business or brand-sensitive details.
Live mode uses:
- `POST /v1/generate`
Observed compatible request shape:
{
"prompt": "A minimal blue geometric logo on white background"Do not include confidential information in prompts unless you are comfortable sending it to Rynjer under its service terms.
A user may not realize from metadata alone that live operation requires a Rynjer token and runtime configuration.
The registry requirements list no required environment variables because mock mode is default, but the live runtime does have optional environment-variable setup. This is disclosed in the README, but not surfaced in the registry metadata.
Set env vars before running the runtime: export RYNJER_USE_LIVE=1 export RYNJER_BASE_URL="https://rynjer.com" export RYNJER_ACCESS_TOKEN="your_access_token_or_ryn_agent_v1_key"
Document optional live-mode credentials and environment variables prominently before enabling live generation.