Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jircik/Visual-Explainernpx agentmods add skills/jircik/visual-explainer/visual-explainerWrote 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/jircik/visual-explainer/visual-explainer)<a href="https://agentmods.dev/skills/jircik/visual-explainer/visual-explainer"><img src="https://agentmods.dev/badge/skills/jircik/visual-explainer/visual-explainer/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/jircik/visual-explainer/visual-explainer"><img src="https://agentmods.dev/badge/skills/jircik/visual-explainer/visual-explainer.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.00071 | $0.01827 |
| Opus 5.5 | $0.00028 | $0.00731 |
| Sonnet 5.5 | $0.00014 | $0.00365 |
| Haiku 4.5 | $0.00007 | $0.00183 |
Grade A, and why
visual-explainer 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 1mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Explainer
Generate an interactive HTML dashboard that visually explains a codebase — its architecture, file structure, data flows, and the purpose behind every meaningful file and function.
When to Use
- User asks to explain, visualize, or document a codebase
- User wants to understand how a project works
- User needs onboarding documentation for a repo
- User asks for architecture diagrams or code maps
When NOT to Use
- Single-file explanations (just explain inline)
- Non-code projects (pure docs, assets)
- The user only wants a README
Output
A self-contained ./visual-explainer/index.html file in the project root. No external dependencies except CDN links (Mermaid.js, Tailwind CSS, Inter font).
Process
Phase 1: Analyze
- Detect the project root. Use the current working directory.
- Read the file tree. Run
find . -type fexcluding:node_modules,.git,dist,build,.next,__pycache__,.venv,target,vendor,.cache, coverage dirs, and lockfiles. - Detect the stack. Identify languages, frameworks, and tools from config files (
package.json,pom.xml,Cargo.toml,pyproject.toml,go.mod,docker-compose.yml, etc.). - Classify files. Sort every file into one of these categories:
- Core — main application logic, entry points, route handlers, services, controllers, models, schemas
- Config — environment, build, lint, CI/CD configs
- Infrastructure — Docker, deployment, IaC
- Test — test files, fixtures, mocks
- Skip — lockfiles, generated code, binary assets,
.gitignore,LICENSE,package-lock.json, etc.
- Read all Core files. Understand:
- What each file does (purpose, not line-by-line)
- Key exports, classes, functions, and why they exist
- How files depend on each other (imports/requires)
- The data flow: entry point → processing → output/response
- Read Config and Infrastructure files. Summarize what they configure and why.
- Skim Test files. Note what they cover, don't explain each test.
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.
- 1mo ago First seen · 168 lines · 71 tokens per session scan A ebb3f52f3289
visual-explainer is a skill published in the GitHub repository jircik/Visual-Explainer (4 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,827 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-08-31.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
answer-me-with-html
Create an offline static HTML technical report only when expressly requested, without running untrusted HTML, shell commands or network requests.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.