explainme

explainme is a skill for Claude Code from jdanigo/hydraia. It costs 125 tokens per session (3,839 once invoked), scanned A, a copy of archify, MIT.

A tool that turns verified code structure into a standalone interactive HTML map. The map can show architecture, workflows, sequences, data flow, or lifecycle states, with source-linked nodes and guided walkthroughs.

In plain words
What is it for?
Use it to create onboarding material, explain a subsystem or pull request, document system behavior, and show how components, calls, storage, or data movement fit together.
Why use it?
It provides a readable explanation of unfamiliar code while keeping the diagram tied to real files and relationships. Validation helps catch diagrams that are structurally or visually inconsistent before delivery.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hydraia plugin — 52 skills, 17 commands, 27 agents, 4 hooks shipped together

Good fit Use it to create onboarding material, explain a subsystem or pull request, document system behavior, and show how components, calls, storage, or data movement fit together.

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

Made for: Claude Code.

Or install hydraia, the plugin that ships this one along with the rest of its 52 skills, 17 commands, 27 agents, 4 hooks.

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 explainme

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jdanigo/hydraia/explainme"><img src="https://agentmods.dev/badge/skills/jdanigo/hydraia/explainme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,839 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 88% copy Near-identical to another mod 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.00125 $0.03839
Opus 5 $0.00063 $0.01920
Sonnet 5 $0.00025 $0.00768
Haiku 4.5 $0.00013 $0.00384

Measured today against content hash 66748ffd1cd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

explainme 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 today.

The scan reads SKILL.md. This mod also ships 35 executable files (bin/archify.mjs, bin/open-artifact.mjs, bin/preview.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

88% identical to archify — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/explainme/SKILL.md · 154 lines

How it starts

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

Explainme — visual, verifiable code explanation

Explain a codebase to a human as a self-contained, interactive HTML map compiled from a small typed JSON specification. The deterministic CLI validates every artifact before delivery and refuses to ship one that is not geometrically clean and semantically faithful — so the diagram never invents topology. Static output is the default; enable motion only for a demo or presentation.

This is a vendored + rebranded build of Archify (MIT). The MIT LICENSE, THIRD_PARTY_NOTICES.md, and the upstream attribution above are kept as required. The engine (schemas, renderers, viewer, validator) is upstream's; Hydraia adds the codegraph grounding and the onboarding framing below.

Hydraia grounding — codegraph is the topology source (read first)

Do NOT hand-guess the system's structure. In Hydraia the topology comes from codegraph (the verified code knowledge graph), and Explainme renders it:

  1. Query codegraph for the subsystem in scope — components/modules, call edges, entry points, storage/transports, blast radius (codegraph_explore, callers/callees/impact). That is the ground truth.
  2. Author the typed IR (below) from those verified nodes and edges — not from a guess. When a node maps to real code, set its source-evidence (SRC markers) from codegraph's file:line so the diagram is click-through to the actual source.
  3. Frame it as onboarding, not decoration. Attach up to ~5 guided-walkthrough views chapters that walk a newcomer through the real paths — e.g. "request path", "auth flow", "data lineage", "startup/lifecycle". The goal is "a new engineer understands this system in 10 minutes", not "a pretty picture".
  4. Then follow the fast authoring path. The model that drives this is Sonnet-class — the hard correctness lives in the deterministic CLI + codegraph, not in the model's geometry planning.

Fast authoring path

Create a self-contained, interactive HTML diagram from a small typed JSON specification. Static output is the default; enable motion only when the user asks for a demo or presentation.

Read the full file on GitHub · 154 lines

Files

What ships with it

60 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.

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. today First seen · 154 lines · 125 tokens per session scan A 66748ffd1cd0

Subscribe to this mod's changes

explainme is a skill published in the GitHub repository jdanigo/hydraia (8 stars, last pushed today), licensed MIT. It adds 125 tokens to every session and 3,839 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to archify, differing in 26 lines, and is treated as a copy.

Related

Other skills, from other repositories

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens

engineering-onboarding

Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…

murphytrueman/design-system-ops · 68 tokens

designer-onboarding

Create an onboarding guide for a designer joining a team that uses a design system. Trigger when someone says: onboard new designer, getting started guide, new team member guide, onboarding documentation, first day with the system, new designer guide, or anything about helping a designer new to the team or the design…

murphytrueman/design-system-ops · 70 tokens

show-me

Explain the current topic or a proposed design visually with types and signatures, pseudocode, a call tree, a component tree, a file tree, a diff, a whole block, a Mermaid diagram, or a published Artifact.

bendrucker/claude · 48 tokens

uiux

Use when deciding how the product's UI should look and how its UX should behave, from the mockup and logic docs - visual direction, design system, and per-screen design chapters via an interview, using capstone's own vendored design method.

GentBajko/capstone · 53 tokens

mockup

Use when defining a new product idea - adaptive purpose/business-plan/scenarios interview persisted to a file, then a traceable markdown mockup.

GentBajko/capstone · 31 tokens