Borrowing it
Nothing to install: this file belongs to sageox/ox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sageox/ox/main/.claude/skills/ox-viz/SKILL.mdgit clone --depth 1 https://github.com/sageox/oxWrote 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/sageox/ox/ox-viz)<a href="https://agentmods.dev/skills/sageox/ox/ox-viz"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-viz.svg" alt="Measured on agentmods" 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.00082 | $0.00238 |
| Opus 5 | $0.00041 | $0.00119 |
| Sonnet 5 | $0.00016 | $0.00048 |
| Haiku 4.5 | $0.00008 | $0.00024 |
Grade A, and why
ox-viz 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 8d 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.
What it actually says
For PR work, run ox viz pr before drafting. For a reviewer question, run
ox viz pr --intent "<question>" --json; apply the selected result's
guidance, then pull its recipe with ox viz <id>. For all other artifacts,
use ox viz suggest "<intent>" and do the same.
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.
- 8d ago First seen · 20 lines · 82 tokens per session scan A 9e1a0b0679c0
ox-viz is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 238 once invoked, about $0.0004 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.
Other skills, from other repositories
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
build-sdf-liquid-glass
Build lightweight SDF/canvas displacement glass with Vaso. Use for responsive refractive cards, no-WebGL fallbacks, many compact surfaces, or explicit SDF requests.
build-webgl-liquid-glass
Build production-ready GPU liquid-glass surfaces with liquid-gl for React or DOM UIs. Default for refractive cards, notifications, panels, GPU bevels, and WebGL glass.
wireframe
A template for an interactive React wireframe, a rough screen design used to plan an interface. It can show several screens, their transitions, and where data fields connect to the interface.
domain-model-diagram
A template for an interactive React domain model diagram, a visual map of the entities and relationships in a software system. It provides grid and focused views with pan, zoom, labels, and category colors.
codebase-design
Design or improve deep modules, small interfaces, real seams, and public-interface tests. Use when shaping a module, placing a dependency seam, evaluating shallow pass-through layers, improving testability, or comparing architecture alternatives; do not force unrelated refactors.