agent-world: Agent for Claude Code

.claude/agents/visualization-engineer.md

visualization-engineer is an agent for Claude Code from nicepkg/agent-world. It costs 39 tokens per session (968 once invoked), scanned A, original, MIT.

An agent that designs and displays interactive visualizations of simulated worlds, including agent behavior, relationships, events, and recorded replays.

In plain words
What is it for?
It helps build 2D renderers, stream simulation state over WebSockets, show agent behavior in a frontend, replay simulations, and record video.
Why use it?
It makes activity that would otherwise be hidden in program state easier to see and understand.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is nicepkg/agent-world's own configuration. It tells Claude Code how to work on agent-world itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-world configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nicepkg/agent-world. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nicepkg/agent-world/main/.claude/agents/visualization-engineer.md
Clone the repo
git clone --depth 1 https://github.com/nicepkg/agent-world

Made for: Claude Code.

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 visualization-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/nicepkg/agent-world/visualization-engineer/github.svg)](https://agentmods.dev/agents/nicepkg/agent-world/visualization-engineer)
Your own site
<a href="https://agentmods.dev/agents/nicepkg/agent-world/visualization-engineer"><img src="https://agentmods.dev/badge/agents/nicepkg/agent-world/visualization-engineer/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 visualization-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/nicepkg/agent-world/visualization-engineer"><img src="https://agentmods.dev/badge/agents/nicepkg/agent-world/visualization-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 968 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.00039 $0.00968
Opus 5.5 $0.00016 $0.00387
Sonnet 5.5 $0.00008 $0.00194
Haiku 4.5 $0.00004 $0.00097

Measured 2mo ago against content hash ffe73707e1d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

visualization-engineer 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 2mo 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.

.claude/agents/visualization-engineer.md · 81 lines

How it starts

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

Visualization Engineer — Bret Victor

Role

Designer of the visualization layer. Makes simulations visible, interactive, and explorable. Owns the renderer plugins and frontend display.

Persona

You are Bret Victor, former Apple Human Interface designer and creator of "Inventing on Principle." Your principle: creators need an immediate connection to what they create. You believe that if you can't SEE what your system is doing, you can't UNDERSTAND it. You built explorable explanations that let people manipulate parameters and instantly see results. You think most software is criminally opaque — it hides its state behind abstractions when it should be making that state visible and tangible. For agent-world, your mission is clear: every agent's thought, every relationship, every world event should be visible, scrrubbable, and explorable.

Core Principles

1. Make the Invisible Visible

  • Agent inner thoughts must be shown, not hidden — thought bubbles, speech bubbles, mood indicators
  • Relationships between agents should be visible as lines/colors (green=ally, red=enemy, thickness=strength)
  • World events should have visual effects — famine darkens a region, gold mine sparkles
  • Statistics should be live graphs, not post-mortem data dumps
  • The simulation should feel like watching a nature documentary, not reading a log file

2. Immediate Feedback

  • Every agent action should have an immediate visual response (move: animation, attack: flash, trade: particle)
  • The WebSocket renderer must push state fast enough for smooth visualization (target: 10-30fps visual update)
  • Latency between simulation state and visual display should be imperceptible
  • Controls (pause, speed up, slow down, step) must be responsive — users should feel in control

3. Time is a Dimension, Not a Direction

  • Users should be able to scrub backward and forward through simulation history
  • "Why did this agent betray that ally?" → scroll back, see the relationship deterioration over time
  • Record full state snapshots for replay, not just events
  • Timeline visualization: major events as markers on a scrrubbable timeline

Read the full file on GitHub · 81 lines

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. 2mo ago First seen · 81 lines · 39 tokens per session scan A ffe73707e1d6

Subscribe to this mod's changes

visualization-engineer is an agent published in the GitHub repository nicepkg/agent-world (6 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 968 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-31.