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-explainer-diffWrote 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-diff)<a href="https://agentmods.dev/skills/jircik/visual-explainer/visual-explainer-diff"><img src="https://agentmods.dev/badge/skills/jircik/visual-explainer/visual-explainer-diff/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-diff"><img src="https://agentmods.dev/badge/skills/jircik/visual-explainer/visual-explainer-diff.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.00087 | $0.01827 |
| Opus 5.5 | $0.00035 | $0.00731 |
| Sonnet 5.5 | $0.00017 | $0.00365 |
| Haiku 4.5 | $0.00009 | $0.00183 |
Grade A, and why
visual-explainer-diff 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Explainer — Diff
Generate an interactive HTML dashboard that visually explains what changed between two git refs — added, modified, and deleted files with annotated purpose, which architecture layers were touched, and how primary data flows shifted.
Companion skill to visual-explainer. That skill explains a codebase at rest; this one explains a codebase in motion.
When to Use
- User asks to visualize, explain, or document a diff, PR, or commit range
- User wants a change report for review or release notes
- User needs to understand the architectural impact of a branch before merging
- User wants to onboard a reviewer to a large PR
When NOT to Use
- Single-line or single-file diffs (just show the diff inline)
- Commits with no meaningful code change (formatting, lockfile bumps)
- The user wants a textual changelog or PR description (use a different tool)
Input
Two git refs. Resolution order:
- Explicit args from the user (
main..feature/x,HEAD~5 HEAD,<sha1> <sha2>) - If on a feature branch:
<default-branch>..HEAD(detect default viagit symbolic-ref refs/remotes/origin/HEAD) - Fallback:
HEAD~1..HEAD
Confirm the chosen range with the user before running if it was inferred.
Output
A self-contained ./visual-explainer/diff.html file in the project root. Same CDN-only stack as visual-explainer (Mermaid.js, Tailwind CSS, Inter font). Does not overwrite an existing index.html.
Process
Phase 1: Collect
- Resolve the range.
git merge-base <base> <head>→ use the merge-base asBASE, the tip asHEAD. - List changed files.
git diff --name-status BASE..HEAD→ bucket into Added / Modified / Deleted / Renamed. - Get stats.
git diff --numstat BASE..HEADfor per-file insertions/deletions. - Get commit list.
git log --oneline BASE..HEADfor the commit narrative. - Skip noise. Lockfiles, generated code, snapshot files,
dist/,build/, vendored deps. Same skip list asvisual-explainer.
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 · 158 lines · 87 tokens per session scan A 3516fa23824b
visual-explainer-diff is a skill published in the GitHub repository jircik/Visual-Explainer (4 stars, last pushed 5mo ago), licensed MIT. It adds 87 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
address-pr-feedback
Comprehensively addresses PR feedback by fetching all comments, deploying parallel agents for critical analysis of each suggestion, making implementation decisions, then systematically implementing fixes with incremental commits and browser validation. Use when you need to systematically process and implement all PR…
address-pr-comments
Fetches unresolved PR comments, categorizes them (must-fix, suggestion, question, nit), proposes fixes or replies for each, and executes approved actions. Use when addressing PR review feedback or when someone requests changes on your PR.
create-pr
Creates a well-structured pull request with product-focused summary, change highlights, and test steps. Auto-detects base branch, links Linear issues from branch name, and pushes if needed. Use when ready to open a PR or when asking to create a pull request.
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
skills-pr-handle
Use when explicitly asked to handle a pull request in the Scenario skills repository, including review comments and skill validation.
pr-handle-comments
Handle review comments received on GitHub for the current branch's PR or a given PR number or URL, by triaging each unresolved thread, fixing what is warranted, pushing, and replying in each thread, when asked to address, fix or answer PR comments. Works in any Scenario repository.