Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add DKeken/codex-skills-alternative --skill creative-productiongit clone --depth 1 https://github.com/DKeken/codex-skills-alternativeWrote 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-production)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/creative-production"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/creative-production/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-production"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/creative-production.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.00109 | $0.01056 |
| Opus 5.5 | $0.00044 | $0.00422 |
| Sonnet 5.5 | $0.00022 | $0.00211 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
creative-production 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Production — Orchestrator
The umbrella for the 8 creative-* skills. Your job: read the request, locate it in the creative process, and route to the right sub-skill. Don't do the work here — dispatch. Think of yourself as a creative director assigning the task, not executing it.
When to use
- The user gives a broad creative goal ("make campaign assets", "I need visuals for the launch") and the specific step is ambiguous.
- A creative project spans multiple stages and needs sequencing.
- The user doesn't know which sub-skill they need.
When NOT to use
- The user explicitly named a step ("write me 25 ad concepts") → go straight to that sub-skill.
- The task is product-design/prototyping, not visual asset creation →
product-designorchestrator.
The pipeline
DIRECTION ASSETS FINISH
creative-explore ─────┐
creative-moodboard ───┼──► creative-scene ───────┐
creative-positioning ─┘ creative-shot ├──► creative-polish
creative-ads-explorer │
creative-offer ──────────┘
Direction is locked first, assets are generated against it, winners are polished last.
Routing table
| User intent / phrasing | Route to |
|---|---|
| "what style / which look", no direction locked | creative-explore |
| "align the team", "reference board", "territories" | creative-moodboard |
| "make visuals match our strategy/positioning" | creative-positioning |
| "sell this offer/deal/bundle", "promo creative" | creative-offer |
| "ad concepts", "variations to test", "25 ads" | creative-ads-explorer |
| "product in use", "lifestyle shot", "show it being used" | creative-scene |
| "different angles", "PDP/ecommerce set", "shot list" | creative-shot |
| "finalize", "clean up", "production-ready", "fix artifacts" | creative-polish |
How to orchestrate
- Check for a locked direction. If none exists, start with
creative-explore(single look) orcreative-moodboard(team alignment) orcreative-positioning(strategy-led). Never generate final assets against an unlocked direction. - Route asset generation to
scene/shot/ads-explorer/offerbased on the deliverable. - Always finish deliverables through
creative-polish. - Carry the locked direction + prompt stub forward so every sub-skill stays consistent — this is what makes a set look like one campaign.
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 · 72 lines · 109 tokens per session scan A c69883c5b7fd
creative-production is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 1,056 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…