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 skills add miketromba/skills --skill astrogit clone --depth 1 https://github.com/miketromba/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/miketromba/skills/astro)<a href="https://agentmods.dev/skills/miketromba/skills/astro"><img src="https://agentmods.dev/badge/skills/miketromba/skills/astro/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/miketromba/skills/astro"><img src="https://agentmods.dev/badge/skills/miketromba/skills/astro.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.00095 | $0.02383 |
| Opus 5 | $0.00048 | $0.01192 |
| Sonnet 5 | $0.00019 | $0.00477 |
| Haiku 4.5 | $0.00010 | $0.00238 |
Grade A, and why
astro 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 9d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro
Astro is an all-in-one web framework for building content-driven websites. It uses island architecture and server-first design to minimize client-side JavaScript. It supports UI frameworks like React, Vue, Svelte, Preact, and Solid via integrations, and is powered by Vite.
Research Process
To answer questions about Astro, spawn a sub-agent to conduct thorough documentation research.
Launch a Research Sub-Agent
Use the Task tool to spawn a sub-agent dedicated to Astro documentation research. Do NOT specify a model (use the default model for comprehensive research quality).
Critical: Provide the sub-agent with a highly detailed prompt that includes:
- Goal - What you are ultimately trying to accomplish
- Context - Why you need this information and how it fits into the larger task
- Specific Questions - Exactly what information you need answered
- Output Requirements - The format and level of detail needed in the response
Task Tool Configuration
Task tool parameters:
- description: "Research Astro docs"
- subagent_type: "generalPurpose"
- model: (DO NOT SPECIFY - use default for thorough research)
- readonly: true
- prompt: (see template below)
Prompt Template for Sub-Agent
Structure your prompt to the research sub-agent as follows:
You are researching Astro framework documentation to help with a specific task.
## Your Research Goal
[Describe exactly what you need to accomplish with this information]
## Context
[Explain why you need this information and how it will be used]
## Specific Questions to Answer
[List the specific questions that need to be answered]
## Research Process
1. First, fetch the documentation index to understand what's available:
URL: https://docs.astro.build/llms.txt
Astro provides curated documentation sets as separate files. Choose the
most relevant one(s) based on the questions above:
**General documentation (pick ONE based on needs):**
- https://docs.astro.build/llms-small.txt - Abridged docs (compact, non-essential content removed). Use for quick lookups and common questions.
- https://docs.astro.build/llms-full.txt - Complete docs (everything). Use when you need thorough or obscure information.
**Topic-specific documentation (fetch alongside or instead of general docs):**
- https://docs.astro.build/_llms-txt/api-reference.txt - API reference (terse, structured API descriptions)
- https://docs.astro.build/_llms-txt/how-to-recipes.txt - How-to recipes (guided examples for adding features)
- https://docs.astro.build/_llms-txt/build-a-blog-tutorial.txt - Blog tutorial (step-by-step beginner guide)
- https://docs.astro.build/_llms-txt/deployment-guides.txt - Deployment guides (deploying to various services)
- https://docs.astro.build/_llms-txt/cms-guides.txt - CMS guides (integrating content management systems)
- https://docs.astro.build/_llms-txt/backend-services.txt - Backend services (Firebase, Sentry, Supabase, etc.)
- https://docs.astro.build/_llms-txt/migration-guides.txt - Migration guides (migrating from other tools)
- https://docs.astro.build/_llms-txt/additional-guides.txt - Additional guides (e-commerce, auth, testing, DAM)
2. Selection strategy:
- For API/config questions → fetch api-reference.txt
- For "how do I add X" questions → fetch how-to-recipes.txt
- For deployment questions → fetch deployment-guides.txt
- For CMS integration → fetch cms-guides.txt
- For backend/third-party services → fetch backend-services.txt
- For migrating from another framework → fetch migration-guides.txt
- For e-commerce, auth, testing → fetch additional-guides.txt
- For beginner/tutorial questions → fetch build-a-blog-tutorial.txt
- For general or broad questions → fetch llms-small.txt (or llms-full.txt if depth needed)
- When unsure → start with llms-small.txt, then fetch topic-specific files as needed
3. These are large text files containing full documentation content.
Search through the fetched content for relevant sections.
4. Fetch multiple files in parallel using WebFetch when the question
spans multiple topics.
## Required Output
[Specify exactly what format and content you need returned]
Provide a comprehensive response with all findings, including relevant code examples, configuration snippets, and step-by-step instructions where applicable.
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.
- 9d ago First seen · 247 lines · 95 tokens per session scan A e327090775c2
astro is a skill published in the GitHub repository miketromba/skills (2 stars, last pushed 13d ago), licensed MIT. It adds 95 tokens to every session and 2,383 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-31.
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…