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 rojim666/SztuCode --skill visualizegit clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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/rojim666/sztucode/visualize)<a href="https://agentmods.dev/skills/rojim666/sztucode/visualize"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/visualize/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/rojim666/sztucode/visualize"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/visualize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.04933 |
| Opus 5.5 | $0.00021 | $0.01973 |
| Sonnet 5.5 | $0.00011 | $0.00987 |
| Haiku 4.5 | $0.00005 | $0.00493 |
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 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 — 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>.htmlin 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 fromdocument.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.
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.
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 · 404 lines · 53 tokens per session scan A c540927abe67
visualize is a skill published in the GitHub repository rojim666/SztuCode (110 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 4,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-30.
Other skills, from other repositories
design-skill
Use BEFORE building or restyling anything a user will see — web/mobile UIs, landing pages, dashboards, components, emails, AND creative work like Three.js/WebGL/canvas/SVG scenes, data-viz, games, and animations — to make it look intentional and polished, not generic; covers tokens, type, color, layout, motion…
frontend-design
Designs and builds distinctive, production-quality frontend interfaces in HTML/CSS, React, or Tailwind: websites, landing pages, marketing pages, dashboards, web applications, interface components, and style overhauls. Classifies the surface as expressive, conventional, or governed by an existing design system, then…
ui-reviewer
Review rendered UI screenshots for hierarchy, spacing, readability, states, consistency, and visual slop.
intelligent-ui
Helps agents choose prose, native controls, dashboards, motion, or 3D from the user's goal. Use when a user asks to explain, teach, compare, or present information visually, asks you to choose a format, requests a video or code-authored animation as the deliverable, or an interactive artifact may improve understanding…
diagram-design
Creates polished, accessible SVG diagrams as EvoFlux Work widgets or project files. Use when a user asks to design, draw, redraw, or polish a software architecture, data flow, API sequence, state machine, ER model, deployment, service journey, or process diagram, or asks to turn Mermaid, draw.io, or Excalidraw content…
design-system
DESIGN.md integration for Forge — ensures visual consistency across all UI tasks through standardized design specifications.