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 veelenga/preview-skills --skill preview-plangit clone --depth 1 https://github.com/veelenga/preview-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/veelenga/preview-skills/preview-plan)<a href="https://agentmods.dev/skills/veelenga/preview-skills/preview-plan"><img src="https://agentmods.dev/badge/skills/veelenga/preview-skills/preview-plan/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/veelenga/preview-skills/preview-plan"><img src="https://agentmods.dev/badge/skills/veelenga/preview-skills/preview-plan.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.00044 | $0.00476 |
| Opus 5 | $0.00022 | $0.00238 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
preview-plan 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 9d 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.
What it actually says
Preview Plan Skill
Plans are hard to review in raw markdown. This skill renders them as navigable HTML with a sidebar TOC and reading progress — so the reviewer can quickly orient, jump between sections, and focus on what matters.
You don't need to wait for the user to ask for preview. If you're writing a plan, pipe it directly.
Agent Usage
# Preview an existing file
./run.sh plan.plan.md
# Pipe generated plan content directly (preferred)
cat <<'EOF' | ./run.sh
# My Plan
## Phase 1: Setup
...
EOF
The script automatically opens the result in the browser. Do NOT open the file manually.
Writing Plans for Best Preview Quality
Structure your plan markdown to take full advantage of the viewer:
- Use
# Titlefor the plan name — displayed in the sidebar header - Use
## Sectionsfor major phases/sections — each becomes a TOC entry - Use
### Subsectionsand#### Details— nested TOC entries with indentation - Use task lists (
- [ ]/- [x]) — the viewer counts completed/total tasks in the sidebar - Use tables for comparisons, risk matrices, field specs
- **Use
\``diffcode blocks** — lines with+/-` get colored highlighting - Use
\``mermaid` blocks — rendered as interactive diagrams - Use blockquotes (
>) for callouts and important notes
Usage
/preview-plan implementation.plan.md
cat design.plan.md | /preview-plan
Options
-o, --output PATH- Custom output path--no-browser- Skip browser, output file path only
File Requirements
- File extensions:
.plan.md,.plan - Encoding: UTF-8
What ships with it
11 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.
- config.sh 1.2 KB runs code
- lib/browser-utils.sh 9.5 KB runs code
- lib/content-utils.sh 6.7 KB runs code
- lib/html-generator.sh 14 KB runs code
- run.sh 7.5 KB runs code
- templates/scripts/common-ui.js 5.1 KB runs code
- templates/scripts/plan-renderer.js 12 KB runs code
- templates/scripts/utils.js 1.8 KB runs code
- templates/styles/common.css 1.6 KB
- templates/styles/layout.css 14 KB
- templates/styles/plan.css 13 KB
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.
- 9d ago First seen · 61 lines · 44 tokens per session scan A 6772610a18fa
preview-plan is a skill published in the GitHub repository veelenga/preview-skills (8 stars, last pushed 29d ago), licensed MIT. It adds 44 tokens to every session and 476 once invoked, about $0.0002 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
experts
Assemble a panel of experts to assess a problem from multiple professional perspectives, surface agreement and disagreement, and deliver a chaired recommendation with clear tradeoffs. Use when the user wants multi-expert judgment, a second opinion, design critique, option comparison, or a recommendation backed by…
create-plan
A guide for creating repository-aware technical plans: written proposals for implementation, refactoring, migration, or design work based on the actual codebase.
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
google-fonts-curator
Recommend high-taste Google Fonts for websites based on brand tone, page type, and visual direction. Use when the user needs font selection, font pairing, or aesthetic judgment within the Google Fonts ecosystem for landing pages, brand sites, editorial pages, portfolios, or digital products.
programmer-motivator
Give calm, technically grounded encouragement to programmers when the user is stuck on a bug, frustrated by debugging, tired, discouraged, blaming themselves after a mistake, asking for motivation or emotional support while coding, wanting someone to stay with them through a hard problem, celebrating a breakthrough…
subagent-orchestrator
Orchestrate subagent workflows for complex tasks that benefit from decomposition, role-based delegation, and parallel execution. Use when Codex should assemble a temporary team of subagents, choose roles from a reusable role library, create a controlled fallback role when no preset role fits, coordinate read-heavy…