A Czech-language explanation workflow for code changes described by a contract, a Git reference range, or a pull request. It explains the background, idea, code path, evidence, user acceptance testing, and a quiz.

Explaining a completed implementation from its context through the code, reporting verification results, and helping someone check their understanding.

It makes an unfamiliar change easier to understand while tying claims to repository files, tests, or pull-request evidence.

wf-explain — Skill for Claude Code and Codex by tomsej: A Czech-language explanation workflow for code changes described by…

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.

agentmods

npx agentmods add skills/tomsej/pi-ext/wf-explain

Any agent

npx skills add tomsej/pi-ext --skill wf-explain

Clone the repo

git clone --depth 1 https://github.com/tomsej/pi-ext

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-explain.svg)](https://agentmods.dev/skills/tomsej/pi-ext/wf-explain)

Your own site

<a href="https://agentmods.dev/skills/tomsej/pi-ext/wf-explain"><img src="https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-explain.svg" alt="Measured on agentmods" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,193 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00063	$0.01193
Opus 5	$0.00032	$0.00596
Sonnet 5	$0.00013	$0.00239
Haiku 4.5	$0.00006	$0.00119

Measured 5d ago against content hash 5a0495afe54b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wf-explain 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 5d 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.

skills/wf-explain/SKILL.md · 57 lines

How it starts

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

/wf-explain — vysvětli změnu

CELÝ VÝSTUP JE ČESKY. Repozitář jen čti a před psaním prozkoumej okolí změny.

Vstup a důkazy

Vstup: contract.md (target branch...HEAD), ref range, číslo nebo URL PR.

Pipeline: důkazy a kroky převezmi z gate a wf-uat reportu.
Standalone: kritéria spoj s testy v diffu a UAT s kontraktem; bez důkazu použij ⚠️.
PR: gh pr view <n> --json title,body,baseRefName,url, gh pr diff <n>, gh pr checks <n>.
HEAD PR čti bez checkoutu: git fetch origin pull/<n>/head; soubory přes git show FETCH_HEAD:<cesta>.
Tvrzení z PR popisu potvrď diffem, testem nebo CI; nic nevymýšlej.

Styl

Používej jeden název pro jednu věc.
Piš aktivně a používej krátká běžná slova.
Jedna věta nebo odrážka obsahuje jednu hlavní myšlenku.
Vynech výplňové úvodní fráze, opakování a marketingová přídavná jména.
Stručnost nesmí odstranit podmínku, hranici ani pozorovatelné chování.
Veď čtenáře plynule od modelu ke kódu.

Sekce v pořadí

Pozadí — přeskočitelný úvod, potom kontext změny.
Intuice — princip na hračkových datech, bez implementace.
Změna shora dolů — jediný průchod architekturou a kódem.
Akceptační kritéria a jejich ověření — uživatelský výsledek + test, gate nebo UAT.
UAT — jak si to ověřit sám — disposable instance a kroky - [ ]; každý ověří jedno chování.
Kvíz — 5 středně těžkých otázek s variantami a vysvětlením.

Změna shora dolů

Začni problémem, výsledným pravidlem a tabulkou ověřených metrik; neznámé = —. Použij zavřené <details> v pořadí: <code>PRINCIPLE</code> → <code>FLOW</code> → <code>STEP</code> → <code>KEPT</code> → <code>VERIFY</code>. Každý <summary> má štítek, název a jednovětý závěr. FLOW ukáže komponenty; STEP důležité symboly a soubory. Ve STEP vnoř jen podstatné soubory; stav je 🟡 <a href="<diff-url>"><code>MODIFIED</code></a> nebo 🟢 <a href="<diff-url>"><code>NEW</code></a> a vede na PR Files či compare. Název souboru je odkaz na HEAD řádky (.../blob/<sha>/<path>#Lx-Ly). URL nehádej; mechanické změny vynech. Ukaž krátký blok v jazyce souboru s výsledným kódem, ne raw diff. Celý diff patří jen do odkazu.

Read the full file on GitHub · 57 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.

5d ago First seen · 57 lines · 63 tokens per session scan A 5a0495afe54b

Subscribe to this mod's changes

wf-explain is a skill published in the GitHub repository tomsej/pi-ext (69 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,193 once invoked, about $0.0003 per session on Opus 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-30.

Code review

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens