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.
npx skills add ikotelkin/claude-skills --skill dialog-treegit clone --depth 1 https://github.com/ikotelkin/claude-skillsWrote 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/ikotelkin/claude-skills/dialog-tree)<a href="https://agentmods.dev/skills/ikotelkin/claude-skills/dialog-tree"><img src="https://agentmods.dev/badge/skills/ikotelkin/claude-skills/dialog-tree/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/ikotelkin/claude-skills/dialog-tree"><img src="https://agentmods.dev/badge/skills/ikotelkin/claude-skills/dialog-tree.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.00126 | $0.01977 |
| Opus 5 | $0.00063 | $0.00988 |
| Sonnet 5 | $0.00025 | $0.00395 |
| Haiku 4.5 | $0.00013 | $0.00198 |
Grade A, and why
dialog-tree 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 11d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dialog Tree
Why
A "question → clarification → clarification" conversation is a depth-first search: the user dives into one branch while the unexplored sibling branches silently pile up in their head. When the tree gets deep, backtracking becomes painful. This skill offloads that bookkeeping into files: an HTML page in the project repo that shows every branch of the discussion as a tree, lets the user mark branches resolved, and delete dead ones.
The tree is built by the assistant, not by the app: the viewer only renders the data file. "Update the tree" means appending nodes to it. The tree doubles as a session conspectus — after context loss (compaction, new session) reading the data file restores the map of what was discussed, how it branched, and what is still open.
Data / view split, file naming
Two files side by side in the project, named after the treeId — a generic name like dialog-tree.html collides as soon as one machine, one static server, or several sessions host more than one tree:
<treeId>-tree.html— the view, a generic dependency-free renderer. Never edited per-project; upgrading the skill = replacing this file wholesale (any file name keeps working).<treeId>-tree-data.js— the data:META,NODES, optionalSTRINGS(UI localization). The only file the assistant edits. Loaded via a script tag, which works both overhttp://localhostand from disk (file://blocksfetchof JSON, but not script tags — that's why the data is a .js file, not .json).
The view derives the data file name from its own: <name>.html → <name>-data.js. So the two names must stay paired — when renaming, rename both, and never rename after the tree is in use without telling the user (bookmarked URLs break; localStorage marks are keyed by origin + treeId, so a file rename itself does not lose marks).
Set up a tree in a project
- Copy
assets/dialog-tree.htmlandassets/dialog-tree-data-template.js(next to this SKILL.md) into the project repo as<treeId>-tree.htmland<treeId>-tree-data.js(e.g.my-api-tree.html+my-api-tree-data.js). If there is no repo, ask the user where to put them. - In
META(data file) set:treeId— a unique project identifier (kebab-case, e.g. the repo name). It keys the localStorage of the user's marks: two trees sharing a treeId, opened from disk, will corrupt each other's marks.builtUpTo— a human-readable marker of how far into the conversation the tree is built (date + a short quote of the last message that was decomposed).
- Decompose the conversation so far into
NODES(rules below). - Show the tree. JS does not execute in chat file viewers, nor in the Claude Code Browser pane for
file://paths outside the project folder — the page looks empty there:- Browser pane (preferred in Claude Code): start a static server over the directory via
preview_start {name:"<name>"}, openhttp://localhost:<port>/<treeId>-tree.html, and give the user that URL — the user never opens files by hand. Start the server at the beginning of every session that works with the tree. Config in.claude/launch.jsonof the working directory (create it if missing; pick the port once and never change it — the user's marks are bound to thelocalhost:<port>origin):
- Browser pane (preferred in Claude Code): start a static server over the directory via
What ships with it
5 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.
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.
- 11d ago First seen · 100 lines · 126 tokens per session scan A f7df2f12b665
dialog-tree is a skill published in the GitHub repository ikotelkin/claude-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 1,977 once invoked, about $0.0006 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-31.
Other skills, from other repositories
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.