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/ideate-visualsnpx skills add danielrosehill/Claude-Visual-Communications-Plugin --skill ideate-visualsgit 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/ideate-visuals)<a href="https://agentmods.dev/skills/danielrosehill/claude-visual-communications-plugin/ideate-visuals"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-visual-communications-plugin/ideate-visuals.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.00021 | $0.00683 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
ideate-visuals 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideate Visuals
Analyze source content and propose visual-communication concepts across multiple categories to enhance the piece.
When to use
- User has set up a project with
/onboard-visual-projectand wants visual ideas - User has content and wants brainstorming on how to visualize key concepts
- User wants to identify gaps in visual storytelling for a piece
Inputs to gather
- Project name — If not active, ask which project to ideate for
- Content review — Optionally, ask if there are specific sections to focus on or types of visuals to emphasize
Procedure
-
Identify active project. Check for project directories in
${CLAUDE_PLUGIN_DATA:-$HOME/.local/share/claude-plugins}/visual-communications/projects/. If multiple projects exist, ask the user which one to ideate for. Read itsproject.yamlfor context. -
Read source material. Load the source files referenced in the project config to understand the content, key sections, themes, and audience.
-
Analyze structure. Identify major topics, complex concepts, data points, and narrative arcs that would benefit from visual support.
-
Propose 5–8 visual ideas. Suggest concepts across these categories:
- Hero/Header Image — Conceptual photography or illustration to set tone
- Explanatory Visuals — Flowcharts, diagrams, infographics, before/after comparisons
- Conceptual Illustrations — Metaphor-based, symbolic, or visual-analogy representations
- Data Visualizations — Charts, graphs, data-driven infographics
- Spot Illustrations & Icons — Small visuals to break text, reinforce points, section dividers
- Interactive/Animated — Animated diagrams, scrollytelling, hover-reveal graphics
- Video Content — Explainer segments, animated infographics, B-roll, text animations
-
Detail each proposal. For each visual, include:
- Visual type and concept
- Purpose (how it enhances the content)
- Recommended placement in the document
- Complexity: simple | medium | complex
- Generation method: text-to-image | image-to-image | diagram | video | other
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.
- 5d ago First seen · 60 lines · 21 tokens per session scan A d1a5d2d0cd8c
ideate-visuals is a skill published in the GitHub repository danielrosehill/Claude-Visual-Communications-Plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 683 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…