mdvs: Skill for Claude Code

.claude/skills/internalize/SKILL.md

internalize is a skill for Claude Code from edochi/mdvs. It costs 121 tokens per session (2,874 once invoked), scanned A, original, MIT.

A step that turns a code diff into a self-contained interactive HTML explanation. A diff is a description of changes between two versions of code; the step also reads the affected code to explain its wider context.

In plain words
What is it for?
Use it after obtaining a diff to explain changed code, its callers and callees, related types, configuration, and the background behind the change.
Why use it?
It helps a developer understand and take ownership of an agent-made change instead of only checking whether it appears correct.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is edochi/mdvs's own configuration. It tells Claude Code how to work on mdvs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mdvs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to edochi/mdvs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/edochi/mdvs/main/.claude/skills/internalize/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/edochi/mdvs

Made for: Claude Code.

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 internalize

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/edochi/mdvs/internalize"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/internalize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,874 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.00121 $0.02874
Opus 5.5 $0.00048 $0.01150
Sonnet 5.5 $0.00024 $0.00575
Haiku 4.5 $0.00012 $0.00287

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

Security

Grade A, and why

internalize 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 10d 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.

.claude/skills/internalize/SKILL.md · 210 lines

How it starts

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

internalize

Purpose

Agents write code faster than humans can absorb it, so understanding — not writing — is the bottleneck. The durable reason to understand isn't to verify (that's the validate step; agents increasingly self-verify) but to participate: you can't steer the next iteration of a system you don't hold in your head, and you can't feel ownership of decisions you never saw made.

This skill is a stateless transform: given a diff and the code it touches, it emits an interactive HTML explainer that rebuilds understanding fast. It does not decide how the diff was obtained, where the output lives, or when to run — those are the caller's concerns (see Inputs / Output).

Inputs (contract)

The caller supplies:

  • A unified diff — from any source: git diff (working tree / staged / a commit range A..B / a PR), a raw patch piped in, or the output of a delta tool. The skill treats it as opaque unified-diff text; it does not care how it was produced.
  • Read access to the touched code — enough of the repo/tree to explore callers, callees, types, and config so the Background is real, not a paraphrase of the diff.
  • (optional) Technical-depth hint — line / module / architecture. Tunes how granularly the code is walked, not whether the wider objective is explained (that's always covered). If absent, infer from diff size (see Guidelines).
  • (optional) Output target — where to write the artifact. If absent, the skill writes to a scratch path and returns it; deciding the durable home is the caller's job.

If invoked ad-hoc with none of these, derive a convenience default (e.g. git diff of the current branch vs its merge-base) — but treat that as a fallback, not part of the skill's responsibility.

Guidelines

Grounding — this skill builds ownership, so it must never manufacture it. Every factual claim about the existing system (Background) and every asserted rationale (Decision log) must trace to code you actually read, or to the diff, commits, or comments themselves. Tag each non-obvious claim by its epistemic tier: (stated) — present in the diff / comment / commit message; (inferred) — your read of the evidence, cite the file or symbol that supports it; (open question) — genuinely unknowable from what you can see, flag it rather than guess. Never present an inference or a guess as a stated fact. An explainer that fabricates the "why" is worse than none — the reader ends up owning a fiction and steers the next iteration wrong.

Read the full file on GitHub · 210 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. 10d ago First seen · 210 lines · 121 tokens per session scan A 92b423a411d3

Subscribe to this mod's changes

internalize is a skill published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 121 tokens to every session and 2,874 once invoked, about $0.0005 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-05.