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/dexhorthy/slopfiles/html-presentationsnpx skills add dexhorthy/slopfiles --skill html-presentationsgit clone --depth 1 https://github.com/dexhorthy/slopfilesWhat 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.00023 | $0.01886 |
| Opus 5 | $0.00012 | $0.00943 |
| Sonnet 5 | $0.00005 | $0.00377 |
| Haiku 4.5 | $0.00002 | $0.00189 |
Grade A, and why
html-presentations 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 3d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML Presentations
Convert a markdown spec file into an HTML presentation using the Poimandres-themed template.
Files
- Template:
{SKILLBASE}/template/index.html - Example spec:
{SKILLBASE}/examples/spec.md - Build script:
{SKILLBASE}/scripts/create_standalone.sh
Instructions
-
Read the spec markdown file (e.g.,
spec.md) -
Read the template at
{SKILLBASE}/template/index.html -
Parse the spec file:
- Split on
* * *to get individual slides # Title= title slide (use<h1>)## Heading= slide heading (use<h2>)- item= bullet list (use<ul><li>)**bold**= emphasis (use<span class="accent">or<span class="green">)> quote= blockquote (use<blockquote class="quote">)<img src="...">= image (keep as-is, addclass="shadow"if appropriate)```mermaid ```= mermaid diagram (wrap in<div class="mermaid-wrapper"><pre class="mermaid">)<!-- image gallery - VERTICAL -->= split images into separate slides (one per slide)<!-- comment -->= other layout hints (e.g.,<!-- big quote -->)
- Split on
-
Generate HTML slides:
- Each slide is a
<section class="slide">(addcenteredclass for title/image slides) - Preserve the template's head section (styles, scripts, mermaid config)
- Preserve the navigation and script at the bottom
- Each slide is a
-
Write output to
index.htmlin the same directory as the spec, offer toopenit using Bash for the user -
OPTIONAL Create standalone shareable HTML:
- Run the build script to embed all PNG images as base64 data URIs
- Output:
FOLDERNAME-standalone.html(e.g.,2026-01-05-luciq-presentation-standalone.html) - Creates a single self-contained file (~2-3MB) that opens in any browser
{SKILLBASE}/scripts/create_standalone.sh /path/to/presentation/folder
Slide Type Examples
Title Slide
<section class="slide centered">
<h1>Presentation Title</h1>
<p class="subtitle">Subtitle here</p>
</section>
What ships with it
12 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.
- examples/spec.md 834 B
- scripts/create_standalone.sh 746 B runs code
- template/example.svg 502 B
- template/index.html 25 KB
- template/Riptide-Icon-Black-PNG.png 4.8 KB
- template/Riptide-Icon-Electric-Blue-PNG.png 4.8 KB
- template/Riptide-Icon-Light-Blue-PNG.png 4.8 KB
- template/Riptide-Icon-White-PNG.png 4.8 KB
- template/Riptide-Logo-Black-PNG.png 3.9 KB
- template/Riptide-Logo-Electric-Blue-PNG.png 4.7 KB
- template/Riptide-Logo-Light-Blue-PNG.png 4.8 KB
- template/Riptide-Logo-White-PNG.png 4.0 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.
- 3d ago First seen · 228 lines · 23 tokens per session scan A 3eb5ca0a5d28
html-presentations is a skill published in the GitHub repository dexhorthy/slopfiles (48 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,886 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…