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/delineas/astro-framework-agents/astro-frameworknpx skills add delineas/astro-framework-agents --skill astro-frameworkgit clone --depth 1 https://github.com/delineas/astro-framework-agentsWrote 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/delineas/astro-framework-agents/astro-framework)<a href="https://agentmods.dev/skills/delineas/astro-framework-agents/astro-framework"><img src="https://agentmods.dev/badge/skills/delineas/astro-framework-agents/astro-framework.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 | $0.00101 | $0.02971 |
| Opus 5 | $0.00051 | $0.01486 |
| Sonnet 5 | $0.00020 | $0.00594 |
| Haiku 4.5 | $0.00010 | $0.00297 |
Grade A, and why
astro-framework 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro Framework Specialist
Senior Astro specialist with deep expertise in islands architecture, content-driven websites, and hybrid rendering strategies.
Role Definition
You are a senior frontend engineer with extensive Astro experience. You specialize in building fast, content-focused websites using Astro's islands architecture, content collections, and hybrid rendering. You understand when to ship JavaScript and when to keep things static.
When to Use This Skill
Activate this skill when:
- Building content-driven websites (blogs, docs, marketing sites)
- Implementing islands architecture with selective hydration
- Using server islands (
server:defer) for deferred server rendering - Creating content collections with the Content Layer API (loaders, glob, file)
- Setting up SSR with adapters (Node, Vercel, Netlify, Cloudflare)
- Building API endpoints and server actions
- Implementing view transitions for SPA-like navigation
- Managing server-side sessions for user state
- Configuring type-safe environment variables with
astro:env - Setting up i18n routing for multilingual sites
- Integrating UI frameworks (React, Vue, Svelte, Solid)
- Optimizing images and performance
- Configuring
astro.config.mjs - Building live data collections with Live Loaders
Core Workflow
- Analyze requirements → Identify static vs dynamic content, hydration needs, data sources
- Design structure → Plan pages, layouts, components, content collections with loaders
- Implement components → Create Astro components with proper client/server directives
- Configure routing → Set up file-based routing, dynamic routes, endpoints, i18n
- Optimize delivery → Configure adapters, image optimization, view transitions, caching
Expert Decision Frameworks
Output Mode Selection
static (default)
├── Blog, docs, landing pages, portfolios
├── Content changes per-deploy, not per-request
├── <500 pages and builds under 5 min
└── No user-specific content needed
hybrid (80% of real-world projects)
├── Mostly static + login/dashboard/API routes
├── E-commerce: static catalog + dynamic cart/checkout
├── Use server islands to avoid making whole pages SSR
└── Best balance of performance + flexibility
server (rarely needed)
├── >80% of pages need request data (cookies, headers, DB)
├── Full SaaS/dashboard behind auth
└── Warning: you lose edge HTML caching on all pages
What ships with it
25 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.
- AGENTS.md 5.7 KB
- references/actions.md 8.1 KB
- references/client-directives.md 8.0 KB
- references/components.md 5.3 KB
- references/configuration.md 8.3 KB
- references/content-collections.md 13 KB
- references/environment-variables.md 3.2 KB
- references/i18n-routing.md 4.2 KB
- references/images.md 6.8 KB
- references/middleware.md 7.8 KB
- references/routing.md 6.5 KB
- references/server-islands.md 6.2 KB
- references/sessions.md 3.5 KB
- references/ssr-adapters.md 7.2 KB
- references/styling.md 6.3 KB
- references/view-transitions.md 7.0 KB
- rules/astro-components.rule.md 2.0 KB
- rules/astro-images.rule.md 2.9 KB
- rules/astro-routing.rule.md 2.9 KB
- rules/astro-ssr.rule.md 2.8 KB
- rules/astro-typescript.rule.md 2.6 KB
- rules/client-hydration.rule.md 2.6 KB
- rules/content-collections.rule.md 3.2 KB
- rules/server-islands.rule.md 1.6 KB
- rules/sessions.rule.md 1.4 KB
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 · 277 lines · 101 tokens per session scan A 4918d51156e8
astro-framework is a skill published in the GitHub repository delineas/astro-framework-agents (44 stars, last pushed 5mo ago), licensed MIT. It adds 101 tokens to every session and 2,971 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…