Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add f-labs-io/agent-html-skills/plugin install html-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/f-labs-io/agent-html-skills/html-spec-planning)<a href="https://agentmods.dev/skills/f-labs-io/agent-html-skills/html-spec-planning"><img src="https://agentmods.dev/badge/skills/f-labs-io/agent-html-skills/html-spec-planning/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/f-labs-io/agent-html-skills/html-spec-planning"><img src="https://agentmods.dev/badge/skills/f-labs-io/agent-html-skills/html-spec-planning.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.00096 | $0.01783 |
| Opus 5 | $0.00048 | $0.00892 |
| Sonnet 5 | $0.00019 | $0.00357 |
| Haiku 4.5 | $0.00010 | $0.00178 |
Grade A, and why
html-spec-planning 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML Spec, Planning & Exploration
Use HTML as the working surface for thinking through problems — brainstorms, alternative explorations, mockups, and implementation plans. Markdown specs over ~100 lines stop getting read; HTML specs get read because they're navigable, visual, and shareable as a link.
Pre-flight — run BEFORE writing the artifact
Invoke html-skills:html-skills-listen (Skill tool) first; it is idempotent. If it returns a URL, inject it verbatim as window.__CLAUDE_SUBMIT_URL__ in the HTML you are about to write, ?t= query string included (a local, single-session loopback handshake — not a credential). If it reported web/sandbox mode, leave that line out; submitToClaude then falls back to clipboard mode.
When to use this skill
- "Write a spec / RFC / design doc / proposal for X"
- "I'm not sure how to approach X — explore the options"
- "Make me an implementation plan for X"
- "Lay out the tradeoffs for X"
- Whenever the planning artifact will be reviewed by humans, or later read by another Claude session for implementation
For tree-shaped idea capture the user edits, use html-mind-map; for N rendered alternatives to compare, use html-brainstorm-grid.
Output requirements
Save with a descriptive filename like <topic>-spec.html or <topic>-plan.html so multiple planning artifacts on one project compose into a readable folder rather than colliding on output.html.
Core structure
A planning artifact has predictable sections. Use them or a deliberate variation:
- Title + one-sentence framing — what this document is and isn't
- Context / problem — what we're trying to solve, who cares
- Constraints — non-negotiables, scope boundaries
- Approach(es) — either one chosen direction or a comparison of N
- Mockups / diagrams — visuals for any spatial or relational concept
- Data flow / sequence — if relevant, an SVG or HTML+CSS diagram
- Implementation plan — concrete steps, files to touch, code snippets
- Open questions — things the writer doesn't know yet, surfaced not buried
- Out of scope — explicit "we are not solving X here" list
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 Changed · +13 lines · +1 tokens per session 7867901c2a8b
- 10d ago First seen · 85 lines · 95 tokens per session scan A 2b5ec686a40e
html-spec-planning is a skill published in the GitHub repository f-labs-io/agent-html-skills (55 stars, last pushed 7d ago), licensed MIT. It adds 96 tokens to every session and 1,783 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…