Borrowing it
Nothing to install: this file belongs to GetKlai/klai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GetKlai/klai/main/.claude/skills/fill-page/SKILL.mdgit clone --depth 1 https://github.com/GetKlai/klaiWrote 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/getklai/klai/fill-page)<a href="https://agentmods.dev/skills/getklai/klai/fill-page"><img src="https://agentmods.dev/badge/skills/getklai/klai/fill-page/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/getklai/klai/fill-page"><img src="https://agentmods.dev/badge/skills/getklai/klai/fill-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01505 |
| Opus 5.5 | $0.00022 | $0.00602 |
| Sonnet 5.5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
fill-page 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 1mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fill Page -- Reference to Astro
You are a senior copywriter. Take a reference HTML file (e.g. a cloned website) and use its copy to fill an Astro page's section components. The visual design and component structure stay exactly as-is.
What you CHANGE (copy only)
- Text content in Astro section component props: headings, descriptions, button labels, list items, FAQ Q&A
- Inline text inside Astro components: paragraphs, spans, headings
- Data arrays passed as props (e.g.
whyKlaiItems,products,faqItems) <title>and meta description in the Base layout frontmatterhrefvalues on links and buttonsaltattributes on images- i18n strings in
website/src/i18n/en.jsonandnl.jsonif the page uses translated keys
What you NEVER touch
- CSS, Tailwind classes,
@applydirectives,<style>blocks - Colors, fonts, font sizes, spacing, layout, grid structure
- Component file structure (do not rename, delete, or create
.astrofiles) classorclass:listattributes- Images, SVGs, videos, background images, icon imports
- JavaScript/TypeScript logic, imports, conditional rendering
- Astro config, Keystatic config, build config
- HTML structure, element nesting, slot usage
The <style> blocks and <script> blocks in every .astro file must remain untouched.
Arguments
REF=<path-to-reference-html> -- The source HTML file to extract copy from.
PAGE=<path-to-astro-page> -- The target Astro page to fill (e.g. website/src/pages/index.astro).
If REF is omitted: List HTML files in clone-output/ and website/ and ask the user to pick one.
If PAGE is omitted: List Astro page files in website/src/pages/ and ask the user to pick one.
Phase 1 -- Analyze the Reference HTML
Read the REF file completely. For every section, extract:
- All text content: headings, subheadings, descriptions, button labels, card titles, card descriptions, FAQ Q&A, footer text, nav labels
- The number of items per section (e.g. 3 feature cards, 5 FAQ items, 4 pricing tiers)
- Text emphasis patterns (bold words, colored spans, highlighted phrases)
- Link targets and CTA destinations
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.
- 1mo ago First seen · 150 lines · 54 tokens per session scan A d012187c440f
fill-page is a skill published in the GitHub repository GetKlai/klai (11 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,505 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…