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 rampstackco/claude-skills --skill creative-directiongit clone --depth 1 https://github.com/rampstackco/claude-skillsWrote 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/rampstackco/claude-skills/creative-direction)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/creative-direction"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/creative-direction/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/rampstackco/claude-skills/creative-direction"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/creative-direction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00170 | $0.02349 |
| Opus 5.5 | $0.00068 | $0.00940 |
| Sonnet 5.5 | $0.00034 | $0.00470 |
| Haiku 4.5 | $0.00017 | $0.00235 |
Grade A, and why
creative-direction 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Direction
Frameworks produce competent output. Coherent output requires a brief.
This skill turns vague creative intent into a structured brief that downstream skills can reference. It does not generate taste. It captures direction, so the dozens of small decisions a project requires (word choice, image selection, white space, sequencing, what to leave out) all answer to the same question.
Worked examples for each axis position can be assembled from any reference brand library that documents tone, aesthetic, audience relationship, and sensory ambition consistently. The framework below describes the four axes; the user's own reference set positions each example along the axes during the brief workflow.
When to use
- The start of a multi-touchpoint project (website, brand, campaign, product launch) where aesthetic coherence matters
- Before running multiple downstream skills that need to share a unified voice and look
- When inheriting a project that has competent execution but feels generic or incoherent
- Recalibrating an existing project that has drifted aesthetically over time
- When the user is a non-curator who knows what feeling they want but cannot articulate the decisions that produce it
When NOT to use
- Use
creative-briefinstead when the user needs a general kickoff brief covering scope, audience, deliverables, and constraints. This skill goes deeper on aesthetic axes specifically, not on the operational layer. - Use
art-directioninstead when briefing a specific creative deliverable (photo shoot, illustration set, video, campaign). This skill produces project-wide aesthetic direction;art-directionextends that direction into specific creative work. - Tactical single-piece work (one tweet, one error message, one button label)
- Projects where the user has complete aesthetic direction documented already (skip to downstream skills)
- Purely functional output (data tables, form labels, system status text)
- Production-stage execution where direction is already locked
- When the goal is to develop taste; this skill codifies intent, it does not develop judgment
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 154 lines · 170 tokens per session scan A fc11c1322566
creative-direction is a skill published in the GitHub repository rampstackco/claude-skills (992 stars, last pushed 5d ago), licensed MIT. It adds 170 tokens to every session and 2,349 once invoked, about $0.0007 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
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the…
frontend
Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain…
ambience-skill
Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typographic reveal (split, blur, shimmer, typewriter, count-up, marquee), scroll storytelling, or card surface…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…