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 musingfox/cc-plugins --skill viz-inlinegit clone --depth 1 https://github.com/musingfox/cc-pluginsWrote 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/musingfox/cc-plugins/viz-inline)<a href="https://agentmods.dev/skills/musingfox/cc-plugins/viz-inline"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/viz-inline/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/musingfox/cc-plugins/viz-inline"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/viz-inline.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00119 | $0.00738 |
| Opus 5.5 | $0.00048 | $0.00295 |
| Sonnet 5.5 | $0.00024 | $0.00148 |
| Haiku 4.5 | $0.00012 | $0.00074 |
Grade A, and why
viz-inline 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 10d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viz Inline Skill
Explain the current topic visually, in chat, with the smallest shape that makes the point clear. Skip the preamble; keep prose brief. No files, no browser — that is viz-render's job.
Shapes
Pick one (rarely more) — the smallest that answers the current question.
Logic / algorithm → pseudocode
on(save)
if content is unchanged
return cached result
write new content
return fresh result
Runtime control flow → call tree
submitForm
createSession
persistPrompt
launchAgent
navigateToSession
UI structure → component tree (keep only the state hooks and module boundaries that matter)
<SessionPage> (src/routes/session.tsx)
useSessionEvents()
<SessionToolbar>
<RunSkillButton> (packages/ui)
File responsibility / refactor scope → shallow file tree (one line of responsibility per entry)
src/
├── commands/ # parses user actions
├── sessions/ # owns session state
└── transport/ # sends API requests
A change to an existing shape → diff syntax (when most of the shape is unchanged, show only what moves; works on any shape above)
submitForm
createSession
persistPrompt
+ expandSkillMention
navigateToSession
+ subscribeToEvents
on(save)
- write content
+ if content is unchanged
+ return cached result
+ write new content
Code shape before code exists → types and signatures
function expandSkill(command: string): string
Component interaction / data flow → small Mermaid (2–8 nodes; if it needs more, it belongs in viz-render)
sequenceDiagram
User->>UI: choose command
UI->>Daemon: send expanded prompt
Daemon-->>UI: stream result
Rules
- Place each visual next to the short text it supports.
- Keep only the calls, files, props, states, and boundaries needed to answer the user's current question — trim everything else.
- Show a whole block only when most of it is new or the user needs a copyable target shape.
What ships with it
1 file 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.
- 10d ago Changed · -3 lines · +5 tokens per session 470577d527c1
- 1mo ago First seen · 119 lines · 114 tokens per session scan A 43dc97f2706e
viz-inline is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 119 tokens to every session and 738 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…