explain-in-html

explain-in-html is a skill for Claude Code from xbklairith/kisune. It costs 100 tokens per session (1,091 once invoked), scanned A, original, MIT.

An HTML presentation workflow for showing diagrams, charts, tables, and other structured explanations in a web page instead of terminal text. It can also present a browser-based round of questions for users to answer.

In plain words
What is it for?
It is for displaying Mermaid, UML, entity-relationship, and state diagrams, dependency graphs, comparison tables, and multi-question forms.
Why use it?
A web page makes relationships and shapes easier to inspect when the structure itself matters. It also gives multi-question interactions more room than a terminal.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the dev-workflow plugin — 28 skills, 1 command, 8 agents, 1 hook, 1 plugin shipped together

Good fit It is for displaying Mermaid, UML, entity-relationship, and state diagrams, dependency graphs, comparison tables, and multi-question forms.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xbklairith/kisune/explain-in-html
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 xbklairith/kisune --skill explain-in-html
Clone the repo
git clone --depth 1 https://github.com/xbklairith/kisune

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 28 skills, 1 command, 8 agents, 1 hook, 1 plugin.

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 explain-in-html

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xbklairith/kisune/explain-in-html"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/explain-in-html.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,091 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.00100 $0.01091
Opus 5.5 $0.00040 $0.00436
Sonnet 5.5 $0.00020 $0.00218
Haiku 4.5 $0.00010 $0.00109

Measured 18d ago against content hash 6d822c8dc991, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

explain-in-html 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 18d 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.

dev-workflow/skills/explain-in-html/SKILL.md · 65 lines

How it starts

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

Explain in HTML

A terminal is a poor renderer for anything with a shape. This skill moves that output to a page.

It owns the medium, not the decision. grilling decides what to interrogate, brainstorming decides what to elicit, scrutinize decides what to review — each keeps that job and hands the rendering here. When one of them owns the decision, it runs first and calls this. Never publish a page to sidestep deciding who should be asking.

Two modes, inferred from content

Content Mode Output
Something to understand — architecture, schema, state machine, a comparison explain A page with diagrams and tables
Something to answer — a question round, a set of choices interact A page with the questions answerable in-browser

Do not ask which mode. Read the content. Mixed content is one page — a short explainer above the questions, never two deliverables.

Default to the page

Use the page whenever the content has structure worth seeing. Fall back to terminal text only for a trivial confirm — a yes/no, a single pick from two obvious options. One question is a sentence; three are a page; at two, use the page if the choices interact.

How to build it

  1. Artifact quickstart with intent: "other" — it returns the page-design contract. Do not also load artifact-design.
  2. Figures — delegate, never improvise. Both of these are built-in skills that own their own rules; do not restate them here, load them.
    • Mechanism — how it works, what talks to what, before/after → artifact-diagramming
    • Quantities — magnitude, distribution, change over time → dataviz, which has hard requirements of its own (run its palette validator; never a dual-axis chart)
    • Within a diagram: Mermaid (<pre class="mermaid">, rendered natively — no CDN) for sequence, state, ER and flow; hand-authored inline SVG for before/after and side-by-side, which Mermaid renders badly.
  3. Publish via Artifact. Interact pages follow grilling's rule — every question carries a recommended answer, so a user who agrees can say "yes to all" and move on. For interact mode declare capabilities: {db: {}, user: {}} — that is what makes answers savable and readable back. Add downloads: true only if the user wants a file too. Explain mode needs none.

Read the full file on GitHub · 65 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. 18d ago First seen · 65 lines · 100 tokens per session scan A 6d822c8dc991

Subscribe to this mod's changes

explain-in-html is a skill published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 100 tokens to every session and 1,091 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

glance-canonical-layouts

Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).

android/skills · 56 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens