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 agentmods add skills/u-ichi/reviewable-html-workbench/plan-previewnpx skills add u-ichi/reviewable-html-workbench --skill plan-previewgit clone --depth 1 https://github.com/u-ichi/reviewable-html-workbenchWrote 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/u-ichi/reviewable-html-workbench/plan-preview)<a href="https://agentmods.dev/skills/u-ichi/reviewable-html-workbench/plan-preview"><img src="https://agentmods.dev/badge/skills/u-ichi/reviewable-html-workbench/plan-preview.svg" alt="Measured on agentmods" 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 | $0.00276 | $0.02470 |
| Opus 5 | $0.00138 | $0.01235 |
| Sonnet 5 | $0.00055 | $0.00494 |
| Haiku 4.5 | $0.00028 | $0.00247 |
Grade A, and why
plan-preview 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-preview
役割
Plan Mode で正式な <proposed_plan> を提示する直前に、同じ計画内容を一時HTML previewとして出す。
このskillは利用者が手でコマンドを打つためのものではない。agentが計画本文を組み立てた段階で plan-preview CLIを呼び、返却JSONの url を <proposed_plan> 内へ自然に入れる。
Plan Mode 中の計画確認プレビューは、このskillが優先入口になる。通常の最終HTML成果物を作る visual-html-renderer の document-model.json → render → validate → preview フローへ流さない。
Role
Create a temporary visual preview for a Plan Mode proposal. The user should not run the CLI manually. The agent calls plan-preview, receives a session-scoped URL, and places that URL naturally inside the <proposed_plan> text. During Plan Mode, plan preview requests should route here instead of the final-artifact visual-html-renderer document-model flow.
Strict procedure profile
- Strictness: strict-procedure。Plan Mode の正式な実装基準は
<proposed_plan>本文であり、previewは判断補助として扱う。 - Hard gates: 外部サービス送信、shared state変更、永続ファイル出力、skill実行時にhookを動的に追加しない（plugin同梱の静的hook定義は対象外）。
- Forcing function:
plan-previewCLI、TTL付き一時ディレクトリ、Plan preview: <url>行、失敗時の明示。 - Completion receipt:
<proposed_plan>内に preview URL またはPlan preview: unavailable (<reason>)を含める。
言語方針 / Language behavior
Follow the language of the latest user request for progress updates, preview labels, and the surrounding plan text. 日本語の計画依頼には日本語で、英語の計画依頼には英語で返す。Plan preview: <url> の固定ラベルは互換性のため英語のまま使ってよい。
発火条件
次のいずれかに当たる場合、このskillを使う。
- ユーザーが plan のグラフィカル表示、図示、preview URL、graphical plan review を求めている。
- ユーザーが Plan Mode 中に「この計画をHTMLでプレビューして」「計画をHTMLで確認したい」のように求めている。
- ユーザーが
preview this plan as HTML,show this plan visually,graphical plan preview,add a plan preview URL,preview the proposed planのように求めている。 - 計画に phase、依存関係、並列worker、検証層、リスク・前提の分岐があり、文字だけでは確認しづらい。
- plugin利用者の体験として、Plan Mode の本文に自然にURLが入っていることが求められている。
Trigger Conditions
Use this skill when the user asks for a graphical plan view, diagrammed plan, preview URL, preview this plan as HTML, show this plan visually, graphical plan preview, add a plan preview URL, or preview the proposed plan. During Plan Mode, use this skill for plan preview requests instead of visual-html-renderer. Also use it when the plan has phases, dependencies, parallel workers, verification layers, or risk branches that are hard to inspect as plain text.
What ships with it
1 file 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.
- 5d ago First seen · 137 lines · 276 tokens per session scan A 496dedc90c91
plan-preview is a skill published in the GitHub repository u-ichi/reviewable-html-workbench (295 stars, last pushed 26d ago), licensed MIT. It adds 276 tokens to every session and 2,470 once invoked, about $0.0014 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.
Other skills, from other repositories
reconcile
Cross-reference a paper against the collection. Finds which cited papers are already collected, which are new leads, which collection papers cite this one, and reconciles all cross-references bidirectionally. Run on a single paper directory or use --all for the entire collection.
author-context
Create a propstore context for one paper with CEL assumptions, parameters, and perspective. Every claim extracted from the paper will reference this context. Required before extract-claims if the paper does not already have one.
author-rules
Author the DeLP rule artifacts (strict, defeasible, properdefeater, blockingdefeater) encoding a paper's stated argument structure. Runs after register-predicates.
paper-retriever
Retrieve a scientific paper PDF given an arxiv URL, DOI, or paper title. Downloads to papers/ directory. Handles open-access retrieval (arxiv direct, Chrome print-to-pdf for publisher-direct HTML, Unpaywall, title-based open-repository search); for paywalled papers it hands off to whichever paper-retriever- access…
register-concepts
Register concepts from a paper into its propstore source branch using pks source propose-concept.
adjudicate
Systematically adjudicate disagreements across a paper collection. Produces ruthless verdicts on who was wrong, what supersedes what, and what the best current understanding is. Organized by topic clusters with actionable replacement values for implementation.