Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DKeken/codex-skills-alternativenpx agentmods add skills/dkeken/codex-skills-alternative/creative-exploreWrote 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/dkeken/codex-skills-alternative/creative-explore)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/creative-explore"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/creative-explore/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/dkeken/codex-skills-alternative/creative-explore"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/creative-explore.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.00111 | $0.01190 |
| Opus 5.5 | $0.00044 | $0.00476 |
| Sonnet 5.5 | $0.00022 | $0.00238 |
| Haiku 4.5 | $0.00011 | $0.00119 |
Grade A, and why
creative-explore 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative — Explore (Visual Direction)
Converge on ONE visual direction before spending generation budget on variations. Picking a direction early is the single highest-leverage creative decision — everything downstream (scenes, shots, ads, polish) inherits it. Never jump straight to final assets without a locked direction.
When to use
- Starting a new brand, campaign, or product visual from scratch.
- The user has a product but no agreed "look".
- Stakeholders disagree on aesthetic and you need concrete options to react to.
- Before
creative-scene,creative-shot,creative-ads-explorer, orcreative-offerwhen no direction is locked.
When NOT to use
- A direction/brand guide already exists → skip to the asset skills.
- You only need to finish one already-chosen image →
creative-polish. - The user wants team-wide mood alignment with territories →
creative-moodboard(broader than this).
Inputs to gather (ask only what's missing)
- Product / brand + what it does, in one line.
- Audience + the feeling it should evoke (trust? excitement? calm?).
- Hard constraints: locked colors, logo, fonts, explicit do-nots.
- Medium: web hero, paid ad, packaging, social, app store.
If the user can't answer "what feeling", propose 2-3 candidate feelings and let them pick — don't stall.
Workflow
- Diverge on directions. Propose 3-6 named directions. Each must differ in organizing principle, not just palette. For each: name, one-line vibe, palette, typography feel, photographic/illustration style, when it wins, when it fails.
- Write a reusable prompt stub per direction, structured
scene/backdrop → subject → details → constraints. This stub is the DNA that downstream skills reuse for consistency. - Generate ONE reference image per direction with your image-generation tool (any text-to-image backend: DALL·E, Imagen, FLUX, SD, Midjourney). Keep it small/fast (
1024x1024). Save to./creative/explore/<direction>.png. - Present side by side with the rationale table. Make a recommendation tied to the audience + medium.
- Lock one (or fuse two). Hand the locked direction + prompt stub to the next skill.
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 · 77 lines · 111 tokens per session scan A fbef3f6610cb
creative-explore is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 4mo ago), licensed MIT. It adds 111 tokens to every session and 1,190 once invoked, about $0.0004 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
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…
email-lifecycle-flow-writer
Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.
work-with-creators-creator-vetting
Vets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated…