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/feliperun/md.html/mdhtml-authornpx skills add feliperun/md.html --skill mdhtml-authorgit clone --depth 1 https://github.com/feliperun/md.htmlWhat 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.00092 | $0.01048 |
| Opus 5 | $0.00046 | $0.00524 |
| Sonnet 5 | $0.00018 | $0.00210 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
mdhtml-author 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdhtml authoring
mdhtml 1.0 turns a Markdown file (optional front matter plus a Markdown body) into a single portable HTML document that renders in the browser and works from disk. The committed templates and examples are the reference material for every convention in this skill: read them, and never re-derive or copy the format.
Workflow
-
Scaffold from a canonical template. Run
mdhtml new <name> --template <kind>with<kind>one ofresume,memo,spec,recipe,chapter. The committed templates are the same material and the starting point when the CLI is unavailable:- templates/resume.md
- templates/memo.md
- templates/spec.md
- templates/recipe.md
- templates/chapter.md
Their built counterparts show the conventions applied end to end:
- examples/resume.md
- examples/memo.md
- examples/spec.md
- examples/recipe.md
- examples/chapter.md
-
Write the front matter. Only the reserved keys in references/front-matter.md are presentation input; everything else is semantic metadata. Keep it minimal:
titleis required,summaryandlangare common, andtheme,toc,sections, andfiguresappear only when the document needs them. -
Write the body in the supported Markdown subset. Headings, paragraphs, links, images, blockquotes, GFM tables, code spans and fences, nested and ordered lists, task lists, emphasis, strong, strike, and footnotes. Raw HTML is not enabled; keep content in Markdown. Every heading receives a deterministic slug, and an explicit
{#id}override replaces it. -
Shape content with containers and section components. Containers are Pandoc-style
:::fences; section components bind to a heading slug through thesections:front matter map. Use only the shapes in references/containers.md and references/section-components.md. Content that misses a shape is not guessed: it degrades to prose andmdhtml checkreportsW-COMP-02.
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.
- 3d ago First seen · 95 lines · 0 tokens per session scan A 52330eb4d615
mdhtml-author is a skill published in the GitHub repository feliperun/md.html (11 stars, last pushed 8d ago), licensed MIT. It adds 92 tokens to every session and 1,048 once invoked, about $0.0005 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…