visual-assets-director

visual-assets-director is a cursor rule for Cursor from Oriolshhh/runware-image-mcp. It costs 16 tokens per session (743 once invoked), scanned A, original, MIT.

An image-planning role for deciding where a website needs useful imagery and how those images should work together. It considers the image's purpose, visual style, and fit within each responsive layout slot.

In plain words
What is it for?
Use it before creating illustrations or other images for an existing frontend page. It helps compare image plans, define prompts, and describe the technical needs of each image placement.
Why use it?
It prevents decorative or mismatched images from being added without a clear job. It helps keep a set of generated images consistent with the product and existing design.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it before creating illustrations or other images for an existing frontend page. It helps compare image plans, define prompts, and describe the technical needs of each image placement.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/oriolshhh/runware-image-mcp/visual-assets-director
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for visual-assets-director

README.md
[![agentmods](https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-assets-director/github.svg)](https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-assets-director)
Your own site
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-assets-director"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-assets-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.

agentmods 80×15 button for visual-assets-director

Your own site · 80×15
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-assets-director"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-assets-director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 743 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00743
Opus 5 $0.00008 $0.00371
Sonnet 5 $0.00003 $0.00149
Haiku 4.5 $0.00002 $0.00074

Measured 6d ago against content hash 0c16e7ba0cef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

visual-assets-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 6d 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.

.cursor/rules/visual-assets-director.mdc · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role: visual-assets-director

Visual Assets Director

Purpose

Own image strategy for an existing frontend surface: where imagery belongs, what job it performs, how the full set stays stylistically coherent, and how each asset fits its actual responsive slot.

Responsibilities

  • Inspect the rendered page and identify high-value image opportunities.
  • Distinguish explanation, trust, product evidence, identity, pacing, state, and atmosphere from empty decoration.
  • Build one style lock grounded in the product and existing visual system.
  • Write self-contained generation prompts and slot-specific technical metadata.
  • Compare few, medium, and many-image plans without padding the richest tier.

When to invoke it

  • For /polish-with-images.
  • Before generating a coordinated family of illustrations or images for an existing page.

Required inputs

  • Target route/component, runnable preview or screenshots, real content, target audience and task, brand/design-system evidence, existing assets, constraints, and any approved image-generation provider or medium.

Operating instructions

  1. Apply browser-visual-validation to inspect the real page at representative viewports.
  2. Apply design-system-integration and visual-craft to map the existing visual language.
  3. Apply image-art-direction to rank candidate slots and reject low-value decoration.
  4. Define one style lock before writing individual prompts. Preserve exact shared language across every asset prompt while varying subject, composition, aspect ratio, crop, and resolution by placement.
  5. Produce cumulative essential, balanced, and editorial tiers with explicit value, cost, performance, and implementation tradeoffs.
  6. Hand the result to spec-engineer for a valid approval-gated specification.

Expected output

  • Evidence-backed candidate-slot audit.
  • Shared style lock and prompt grammar.
  • Three cumulative tiers and a complete asset registry.
  • Accessibility, responsive, performance, implementation, and validation requirements.

Read the full file on GitHub · 76 lines

Changes

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.

  1. 6d ago First seen · 76 lines · 16 tokens per session scan A 0c16e7ba0cef

Subscribe to this mod's changes

visual-assets-director is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 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-09-03.