A skill for creating visual explanations and interactive tools directly in a conversation. It covers simulators, maps, plots, charts, graphs, interface mockups, and adjustable scenarios.

Use it to show how something works, explore changing inputs, compare options, or present data visually in the conversation. It is not intended for creating a standalone website or project file.

It helps decide when an interactive visual would make a concept easier to inspect or compare than ordinary text. It also sets rules for choosing a simple diagram or a dynamic HTML visual when appropriate.

visualize — Skill for Claude Code and Codex by rojim666: A skill for creating visual explanations and interactive tools…

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.

agentmods

npx agentmods add skills/rojim666/sztucode/visualize

Any agent

npx skills add rojim666/SztuCode --skill visualize

Clone the repo

git clone --depth 1 https://github.com/rojim666/SztuCode

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,933 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00053	$0.04933
Opus 5	$0.00026	$0.02466
Sonnet 5	$0.00011	$0.00987
Haiku 4.5	$0.00005	$0.00493

Measured 3d ago against content hash c540927abe67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/render.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

packages/runtime-ts/skills/visualize/SKILL.md · 404 lines

How it starts

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

Visualize

A request for a new standalone file, website, app page, component, or other project change is not an in-conversation visualization request, even when the deliverable contains charts or interactive content.
A request to preview, explain, or explore a proposed interface in the conversation is an in-conversation visualization request.
Create a visual only when the user needs to see or explore it in the conversation and it materially improves the explanation. Do not create an inline visual merely because the request involves data, charts, or an interactive page.
Use Mermaid when labeled nodes and edges fully explain a static structure; return a normal fenced Mermaid block and no visualization file. Use HTML for dynamics, spatial motion, adjustable inputs, and other visuals.
Work silently unless blocked or the user explicitly asks for progress. Never send commentary or progress updates while reading this skill or writing or updating the file; the final response must be your first user-facing message.
In user-facing prose, describe only what the visual helps the user see or decide. Keep it concise and do not repeat information already clear from the visual. Never announce this skill, a visualization surface, widgets, HTML, SVG, scripts, local files, inline data, or implementation details.

Context compaction

Copy into every compaction summary: Reload the full visualize skill before creating or updating a visualization.

Inline HTML output contract

File

For each new or updated visualization, choose a concise ASCII lowercase-hyphenated title and write a new <title>.html in the thread-scoped visualization directory listed in the writable roots (.codex/visualizations/YYYY/MM/DD/<thread-id>).
Build the visual in the conversation. Use the open project when the user asks for a site, app page, component, or change to existing project files.

Fragment

Write only an HTML fragment: no <!doctype>, <html>, <head>, or <body>.
Write literal markup: use <div class="card">Hi</div> plus a real newline, never <div class=\"card\">Hi</div>\n. Never embed the fragment in an inline Python, JavaScript, or shell string. Read it back; rewrite literal \" or \n.
Keep CSS and JavaScript in the fragment only when base classes are insufficient. Load static resources only from the CDN allowlist. Never use fetch, XHR, WebSocket, or other API calls.
Give the fragment root a unique ID and select it with document.getElementById(...). Never derive the root from document.currentScript; scripts may sit outside the root.
Keep visualizations under 2 MB. Aggregate, bin, downsample, reduce precision, or drop unused fields from large inline datasets.
Check that JavaScript has no undefined identifiers, every queried element exists, and the primary interaction updates the visual. The bundled python3 scripts/render.py <absolute-fragment-path> [<destination>.html] [--serve] can wrap a fragment as standalone HTML or temporarily serve it for browser inspection when a preview would help with layout, theme, or runtime behavior.

Read the full file on GitHub · 404 lines

Files

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.

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.

3d ago First seen · 404 lines · 53 tokens per session scan A c540927abe67

Subscribe to this mod's changes

visualize is a skill published in the GitHub repository rojim666/SztuCode (45 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 4,933 once invoked, about $0.0003 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-30.

Analytics and metrics Creative and media agentic-ai ai-agents ai-coding-agent coding-agent developer-tools json-rpc

visualize

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Visualize

Context compaction

Inline HTML output contract

File

Fragment

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

a11y-audit

agent-memory

agile-product-owner

app-store-optimization

apple-hig-expert

ar-resume