Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/lfurze/claude-skillsnpx agentmods add skills/lfurze/claude-skills/astro-websiteWrote 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/lfurze/claude-skills/astro-website)<a href="https://agentmods.dev/skills/lfurze/claude-skills/astro-website"><img src="https://agentmods.dev/badge/skills/lfurze/claude-skills/astro-website/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/lfurze/claude-skills/astro-website"><img src="https://agentmods.dev/badge/skills/lfurze/claude-skills/astro-website.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.00122 | $0.01673 |
| Opus 5.5 | $0.00049 | $0.00669 |
| Sonnet 5.5 | $0.00024 | $0.00335 |
| Haiku 4.5 | $0.00012 | $0.00167 |
Grade A, and why
astro-website 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 2mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro Website Builder
Build polished, multi-page static websites from provided content using Astro 5, deployed to Cloudflare Pages with custom domains.
When This Skill Applies
The user provides content in one of these forms (placed in the project root before starting):
- Markdown (.md) articles
- A PDF or eBook on a topic
- A collection of text files on a theme
- A WordPress XML export
- Sometimes just a topic and verbal description
The job is to transform that into a professional, fast, accessible website.
Before Starting: Gather Requirements
Ask these questions (skip any already answered):
- Site name and domain — What's it called? What custom domain? (e.g., myproject.com)
- Purpose and audience — Who is this for?
- Content sections — What pages should the site have? (Suggest a structure based on the provided content)
- Theme preference — Dark mode default, light mode, or both with toggle? Color preferences?
- Font style — Editorial/serif, clean modern, or technical? (See
references/design-tokens.mdfor options)
Project Initialization
Run in the empty project folder:
npm create astro@latest . -- --template minimal --typescript strict --install --git --no
npm install @astrojs/sitemap marked sanitize-html
Create the folder structure:
src/
├── components/ # Header, Footer, cards, reusable UI
├── layouts/ # BaseLayout.astro
├── pages/ # File-based routes
├── data/ # Content as TypeScript arrays
├── styles/ # global.css
└── utils/ # Helpers (if needed)
public/
├── images/
├── fonts/ # Self-hosted fonts (if any)
├── favicon.svg
├── favicon.ico
├── robots.txt
└── _headers
Create these config files:
astro.config.mjs:
import { defineConfig } from 'astro/config';
import sitemap from '@astrojs/sitemap';
export default defineConfig({
site: 'https://[your-domain.com]',
integrations: [sitemap()],
});
wrangler.jsonc:
{
"name": "[project-name]",
"compatibility_date": "[YYYY-MM-DD]",
"assets": { "directory": "./dist" }
}
What ships with it
3 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.
- 2mo ago First seen · 180 lines · 122 tokens per session scan A 486ead9e456e
astro-website is a skill published in the GitHub repository lfurze/claude-skills (24 stars, last pushed 7mo ago), licensed MIT. It adds 122 tokens to every session and 1,673 once invoked, about $0.0005 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.