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 Cloudgeni-ai/opengeni --skill visualizegit clone --depth 1 https://github.com/Cloudgeni-ai/opengeniWrote 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/cloudgeni-ai/opengeni/visualize)<a href="https://agentmods.dev/skills/cloudgeni-ai/opengeni/visualize"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/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/cloudgeni-ai/opengeni/visualize"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/visualize.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.00072 | $0.07149 |
| Opus 5.5 | $0.00029 | $0.02860 |
| Sonnet 5.5 | $0.00014 | $0.01430 |
| Haiku 4.5 | $0.00007 | $0.00715 |
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 yesterday.
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 — 321 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 a normal Markdown table when the user asks for a table; return it directly and do not create a visualization file.
- Custom image sizing or gallery layout is also an inline HTML use case, even without interactive controls.
- Use normal Markdown for a static explanation that needs no interaction. Use HTML for dynamics, spatial motion, adjustable inputs, and other visuals.
- 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. Avoid unsolicited implementation commentary; explain the implementation when the user asks.
Context compaction
Reload this Skill before creating or updating an inline visualization after compaction.
Inline HTML output contract
Message source
- Write the visualization directly into your reply in an
opengeni-htmlfenced code block. The timeline retains and renders this HTML; no sandbox file or upload is required. - Ordinary
htmlcode blocks remain source code. Use the dedicated fence for visuals rendered in chat, including static galleries and diagrams. - For workspace tools, include
<script src="/__opengeni/site-tools/client.js"></script>before your own scripts, then callcreateOpenGeniSiteClient(). Discover exact tool names and schemas before authoring calls. This uses the existing viewer permissions and approval flow. Never put credentials, workspace ids, or deployment URLs in the fragment. Usesitesfor a saved, reusable page or app. - 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.
- Do not create a Site or publish a file merely to show a self-contained visualization.
What ships with it
2 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.
- yesterday First seen · 321 lines · 72 tokens per session scan A 7aced97bd3bf
visualize is a skill published in the GitHub repository Cloudgeni-ai/opengeni (205 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 7,149 once invoked, about $0.0003 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-10-21.
Other skills, from other repositories
generative-ui
Use when presenting information already in hand as a small, static structured panel in the conversation — status, results, comparisons, or a compact summary — rather than prose, a markdown table, a widget, or an app.
st-widget-builder
Use when the user asks to render, build, visualise, mock up, or show a widget (chart, dashboard, card, table, graph) in the Mewbo Console. Teaches how to delegate the work to the st-widget-builder sub-agent instead of writing HTML or inline code yourself.
pn-render-verify
Re-read a rendered or visual artifact and produce a structured verdict against the spec. Use before pn-skeptic-challenge in design workflows when the deliverable is a render, image, screenshot, or HTML page.
pn-animation
Motion roles (Reveal/Orient/Confirm/Delight) and budgets. Use when designing or auditing a motion system — load pn-gsap for GSAP API.
pn-design-variants
Generate 3+ radically different designs or API interfaces in parallel using sub-agents, then compare and synthesize. Based on "Design It Twice" from A Philosophy of Software Design. Use before committing to a single design approach — for UI layouts, component APIs, module interfaces, or system architecture choices.
pn-color-system
Color system design and implementation: OKLCH color space, tinted neutrals, palette structure, contrast, dark mode architecture, and token hierarchy. Use when establishing color tokens, theming, dark mode, or reviewing color choices.