Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/rijul1204/rashedul-agentic-engineering/html-output)<a href="https://agentmods.dev/skills/rijul1204/rashedul-agentic-engineering/html-output"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/html-output.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.1 | $0.00142 | $0.03080 |
| Opus 5 | $0.00071 | $0.01540 |
| Sonnet 5 | $0.00028 | $0.00616 |
| Haiku 4.5 | $0.00014 | $0.00308 |
Grade A, and why
html-output 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 6d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
html-output
Render the current plan, spec, design doc, or conversation context as one self-contained HTML file that conveys the information more densely than markdown can — tables, inline SVG diagrams, semantic structure, in-page navigation, mobile-responsive layout, no external runtime dependencies.
See README.md for the sources that inspired this skill (Thariq Shihipar, Andrej Karpathy) and a before/after demo.
This skill owns what to convert and where to put the file. Visual quality (typography, color, motion, layout polish) is delegated to the frontend-design skill — if it's installed, treat this skill as composing on top of it. Otherwise default to a clean modern editorial style.
When to invoke
Fire on any of:
- The user types
/html-output(optionally followed by a path). - The user asks to "make this an HTML page", "render as HTML", "export to HTML", "give me a shareable version", "make a web version of this".
- The user uses the Karpathy phrasing: "structure your response as HTML", "give me this as HTML", "put this in an HTML file".
- The user asks for a slideshow / deck: "present this as slides", "make a slide deck", "turn this into a slideshow", "give me this as slides" — route to the deck mode below.
- The user finishes a long plan / spec / design doc and wants a more readable artifact.
Do not fire on:
- Source < 30 lines (ask first — HTML overhead is rarely worth it; a slideshow needs ≥ ~5 logical sections to be worth it).
- Source is already HTML (refuse, point at the existing file).
- Live dashboards needing data refresh (out of scope — redirect to a real Next.js page).
Source selection
Pick the source in this order; stop at the first match:
- Explicit path passed as argument.
/html-output /path/to/file.md→ that file. Resolve relative paths against the cwd. If the file doesn't exist or isn't readable, stop and tell the user. @-referenced markdown file in the user's most recent message → that file.- Most recently modified plan file under
/Users/rijul/.claude/plans/*.md— but only if a plan-mode session just exited or the user explicitly says "the plan". Pick bymtime, not name. - Conversation context (last resort): assemble a synthesis from the recent conversation. Only use this branch when the prior three failed AND the conversation contains enough material (≥ ~30 substantive turns). Otherwise ask the user what to convert.
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.
- 6d ago First seen · 139 lines · 142 tokens per session scan A 7378844c78c2
html-output is a skill published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 3,080 once invoked, about $0.0007 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
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
pdf-text-replace
Replace text in fillable PDF forms by updating form field values. This skill should be used when users need to update names, addresses, dates, or other text in PDF form fields.
johnny-suede-design
Suede Labs AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to…
suede-design
Suede Labs AI design skill for making an interface feel intentional instead of templated: design tokens, color strategy, OKLCH ramps, type scale, fluid type, visual hierarchy, dark mode, spacing, component laws, motion, and source-to-implementation visual QA. Use when asked to design, restyle, polish, or audit a…