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 agentmods add skills/danielrosehill/claude-visual-communications-plugin/visual-style-referencenpx skills add danielrosehill/Claude-Visual-Communications-Plugin --skill visual-style-referencegit clone --depth 1 https://github.com/danielrosehill/Claude-Visual-Communications-PluginWrote 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/danielrosehill/claude-visual-communications-plugin/visual-style-reference)<a href="https://agentmods.dev/skills/danielrosehill/claude-visual-communications-plugin/visual-style-reference"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-visual-communications-plugin/visual-style-reference.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00654 |
| Opus 5 | $0.00012 | $0.00327 |
| Sonnet 5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
visual-style-reference 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Style Reference
Display resolution guidelines for different publishing platforms and curated style-modifier vocabulary to enhance visual prompts.
When to use
- User is planning a project and wants platform-specific resolution specs
- User is writing a prompt and wants style modifiers for professional, technical, editorial, or friendly aesthetics
- User wants to ensure visuals are correctly sized for their target platform
Inputs to gather
Optional: user can ask about a specific platform or style category. If none provided, display full reference.
Procedure
-
Determine user need. If user asks about a platform (web, print, social, presentation, whitepaper), show resolution guidelines for that platform. If asking about style (professional, technical, editorial, friendly), show vocabulary for that category.
-
Display resolution guidelines. Show the reference table:
Platform Recommended Resolution Notes ────────────────────────────────────────────────────────────────── Web/Blog 1920x1080 or 1200x800 Optimize for fast loading Print Magazine 300 DPI, actual size Request CMYK-friendly colors Social Media Platform-specific Square (1080x1080) works broadly Presentation 1920x1080 16:9 aspect ratio Whitepaper 1200x800 or full-page Balance quality and file size -
Display style modifier vocabulary. Show categories with examples:
Professional / Corporate • "clean, modern design" • "professional color palette" • "minimal, elegant composition" • "corporate aesthetic" • "sleek and polished" Technical / Detailed • "technical illustration style" • "blueprint aesthetic" • "isometric 3D rendering" • "schematic diagram style" • "engineering-focused composition" Editorial / Journalistic • "editorial illustration" • "magazine-quality photography" • "conceptual art" • "thought-provoking composition" • "narrative visual style" Friendly / Accessible • "warm, approachable style" • "hand-drawn illustration feel" • "friendly cartoon style" • "inviting and approachable" • "personable and relatable"
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.
- 3d ago First seen · 80 lines · 24 tokens per session scan A 6b51882bdd92
visual-style-reference is a skill published in the GitHub repository danielrosehill/Claude-Visual-Communications-Plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 654 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…