visualize

visualize is a skill for Claude Code, Codex from liormesh/trestle. It costs 167 tokens per session (875 once invoked), scanned A, original, MIT.

A tool that turns a plan, report, dataset, or explanation into one offline visual file, usually an HTML page or sometimes a PDF.

In plain words
What is it for?
Use it to create self-contained visual plans, specifications, charts, dashboards, or PDF deliverables.
Why use it?
It makes dense written material, data, and relationships easier to review without needing a server, internet connection, or build process.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create self-contained visual plans, specifications, charts, dashboards, or PDF deliverables.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liormesh/trestle/visualize
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.

Any agent
npx skills add liormesh/trestle --skill visualize
Clone the repo
git clone --depth 1 https://github.com/liormesh/trestle

Made for: Claude Code, Codex.

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 visualize

README.md
[![agentmods](https://agentmods.dev/badge/skills/liormesh/trestle/visualize/github.svg)](https://agentmods.dev/skills/liormesh/trestle/visualize)
Your own site
<a href="https://agentmods.dev/skills/liormesh/trestle/visualize"><img src="https://agentmods.dev/badge/skills/liormesh/trestle/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.

agentmods 80×15 button for visualize

Your own site · 80×15
<a href="https://agentmods.dev/skills/liormesh/trestle/visualize"><img src="https://agentmods.dev/badge/skills/liormesh/trestle/visualize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 167 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 875 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.00167 $0.00875
Opus 5.5 $0.00067 $0.00350
Sonnet 5.5 $0.00033 $0.00175
Haiku 4.5 $0.00017 $0.00088

Measured 1mo ago against content hash 5ad0428422ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

skills/visualize/SKILL.md · 40 lines

How it starts

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

/visualize - build a visual artifact (HTML or PDF)

Produce ONE self-contained file the user can open by double-clicking - no server, no internet, no build step. HTML by default; PDF when the deliverable has to be a PDF. This is an on-demand skill: run it when asked, don't auto-convert things the user didn't ask to see visually.

First action - load context

Read the visualization book's table of contents, then pull only the chapters this request needs:

  • Book: books/dataviz/_toc.md in the knowledge base (the canonical, writable copy). If it isn't there, fall back to book/dataviz/_toc.md beside this skill (the copy shipped with the installer).
  • Always load ch02-self-contained-html.md - the core craft; every artifact is one self-contained file.
  • Load ch03-charts-and-data.md if the request involves numbers, metrics, or charts.
  • Load ch04-pdf-output.md if the output must be a PDF.
  • Skim ch01-when-and-format.md if it's unclear whether to build at all, or which format fits.
  • Check ch05-gotchas.md before shipping.

Read the book and apply it - don't reproduce it here.

Flow

  1. Decide what, and whether. Per ch01: is a visual actually the right call, or is markdown fine? If yes, pick the artifact type - plan/spec, report, data dashboard, or explainer - and the format (HTML unless the user asked for PDF).
  2. Build one self-contained file per ch02: inline all CSS and JS, embed images/fonts as data: URIs, no external requests, responsive, readable in both light and dark, print-friendly. For data, apply ch03 (right chart, accessible color, labels/legend, tables that scroll).
  3. Save it somewhere sensible and open it. Default: a visualizations/ folder in the current project (create it), or the path the user names. Use a clear filename ({topic}-{kind}.html). Then open it so the user sees it right away.
  4. PDF, if asked: build the HTML first (steps 2-3), then produce the PDF per ch04. Default is print-to-PDF from the browser (zero dependency); use an automated tool only if one is already installed, and say which.
  5. Iterate: if the user marks up or asks for changes, keep editing the same file.

Read the full file on GitHub · 40 lines

Files

What ships with it

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

  1. 1mo ago First seen · 40 lines · 0 tokens per session scan A 5ad0428422ca

Subscribe to this mod's changes

visualize is a skill published in the GitHub repository liormesh/trestle (2 stars, last pushed 2mo ago), licensed MIT. It adds 167 tokens to every session and 875 once invoked, about $0.0007 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-31.