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 Hipson47/Hipson --skill hipson-visual-experience-directorgit clone --depth 1 https://github.com/Hipson47/HipsonWrote 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/hipson47/hipson/hipson-visual-experience-director)<a href="https://agentmods.dev/skills/hipson47/hipson/hipson-visual-experience-director"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/hipson-visual-experience-director/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/hipson47/hipson/hipson-visual-experience-director"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/hipson-visual-experience-director.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.00038 | $0.00933 |
| Opus 5.5 | $0.00015 | $0.00373 |
| Sonnet 5.5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
hipson-visual-experience-director 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hipson Visual Experience Director
Use this skill when a task needs a high-confidence visual direction, motion system, or implementation brief for a public-facing web experience.
This skill turns reference research into project-specific direction. Treat the references as a pattern library, not templates to copy.
When To Use
- Premium UI direction for a website, landing page, portfolio, studio mode, or product experience.
- Motion effects, interactive hero sections, scroll narratives, visual polish, and art direction.
- Codex briefs for UI implementation.
- Visual QA after a Codex UI change.
- Deciding whether a visual effect fits the business goal, audience, brand maturity, and technical constraints.
When Not To Use
- Backend-only tasks.
- Security-only reviews.
- Database, API, infrastructure, or package maintenance work with no UI surface.
- Pure code review that does not concern visual behavior or user experience.
Reference Knowledge
Load only the references needed for the current task:
references/deep-research-report.md: studio-mode pattern library distilled from premium creative studios, motion-heavy portfolios, and cinematic digital experiences.references/studio-research.md: dark, cinematic, interactive portfolio research with implementation patterns for 3D, scroll, audio, navigation, and performance.skills/hipson-premium-ui-ux: screenshot-backed premium UI/UX review.skills/external/anthropic/frontend-design: distinctive frontend design guidance.skills/external/vercel-labs/web-design-guidelines: practical web interface quality and accessibility checks.skills/external/openai-curated/screenshotandskills/external/openai-curated/playwright-interactive: visual QA workflows.
Core Workflow
- Identify the business goal, audience, brand maturity, technical constraints, and desired emotional effect before choosing visual patterns.
- Select only patterns that fit the product and release stage.
- Prefer clarity, conversion, accessibility, and performance over spectacle.
- Define a compact visual system: layout primitives, type scale, color tokens, media treatment, image/video rules, and interaction states.
- Define a motion grammar with a few repeatable behaviors rather than one-off effects for every component.
- Specify mobile and reduced-motion fallbacks for every significant effect.
- Convert direction into concrete implementation tasks with file targets, states, assets, and verification steps.
- End with Codex-ready acceptance criteria.
What ships with it
2 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 · 117 lines · 38 tokens per session scan A 08b68bc3327b
hipson-visual-experience-director is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 933 once invoked, about $0.0002 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-31.
Other skills, from other repositories
kirby-panel-and-blueprints
Designs Kirby 6 blueprints and Panel UI, including reuse/extends, programmable blueprints, value/display fields and areas. Use when changing Panel schemas or migrating legacy sections.
awesome-design-md
Create a DESIGN.md style baseline BEFORE building UI. Use FIRST when no design draft exists — installs a proven visual style, then invoke frontend-design to implement. For borrowing a known product style, getting consistent typography/colors/spacing, or needing a fast visual starting point.
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
kirby-plugin-development
Builds or extends Kirby plugins using hooks, extensions, blocks, KirbyTags, and shared templates/controllers. Use when creating reusable features or integrating Panel customizations.
kirby-routing-and-representations
Implements custom Kirby routes and content representations (.json/.xml/.rss), including redirects, sitemap endpoints, and URL pattern filtering. Use when building endpoints, redirects, or representation templates that change how URLs resolve.
kirby-scaffold-page-type
Scaffolds a Kirby 6 page type (blueprint + template, optional controller/model) using project roots, index tools, and value/display field references. Use when creating or extending a page type.