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 fusengine/agents --skill astro-deploymentgit clone --depth 1 https://github.com/fusengine/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/fusengine/agents/astro-deployment)<a href="https://agentmods.dev/skills/fusengine/agents/astro-deployment"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-deployment/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/fusengine/agents/astro-deployment"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-deployment.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.00036 | $0.01414 |
| Opus 5.5 | $0.00014 | $0.00566 |
| Sonnet 5.5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
astro-deployment 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 20d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Also covers output-mode selection (static/server, per-page prerender), Astro 7's stable route caching (cache provider + routeRules, experimental CDN providers per adapter) alongside platform ISR (Vercel isr, Cloudflare KV, stale-while-revalidate headers), and edge middleware for auth/redirects/A-B testing. Does not cover Astro DB setup itself (astro-db) or Islands hydration directives (astro-islands) beyond what's needed to pick a server adapter.
Astro Deployment
Production deployment for Astro 7 across all major platforms — Cloudflare, Vercel, Netlify, and Node.js.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze astro.config.mjs, output mode, and existing adapter
- fuse-ai-pilot:research-expert - Verify adapter docs via Context7/Exa for target platform
- mcp__context7__query-docs - Check Astro 7 adapter compatibility and breaking changes
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Deploying Astro to Cloudflare Workers with D1/KV/R2 bindings
- Configuring Vercel Serverless or Edge runtime with image CDN
- Setting up Netlify Edge Functions
- Running Astro as standalone Node.js server
- Implementing ISR (Incremental Static Regeneration) patterns
- Configuring edge middleware for auth/redirects
Adapter Matrix
| Platform | Package | Runtime | Notes |
|---|---|---|---|
| Cloudflare | @astrojs/cloudflare v14 (Astro 7) |
workerd | astro dev runs on workerd since Astro 6 (v13) |
| Vercel | @astrojs/vercel v11 |
Node/Edge | Image CDN built-in |
| Netlify | @astrojs/netlify v8 |
Edge | Deno-based edge functions |
| Node.js | @astrojs/node v11 |
Node | Standalone server mode |
What ships with it
8 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.
- references/cloudflare-adapter.md 3.2 KB
- references/edge-middleware.md 2.3 KB
- references/isr-patterns.md 3.3 KB
- references/netlify-adapter.md 1.5 KB
- references/node-adapter.md 1.5 KB
- references/templates/cloudflare-setup.md 2.0 KB
- references/templates/vercel-setup.md 1.8 KB
- references/vercel-adapter.md 1.9 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.
- 20d ago Changed 1b6236a13454
- 1mo ago Changed 9db32e52b1e5
- 1mo ago First seen · 106 lines · 36 tokens per session scan A b5285fd5b488
astro-deployment is a skill published in the GitHub repository fusengine/agents (32 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 1,414 once invoked, about $0.0001 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
modal
Modal is a serverless cloud platform for running Python on demand, including on-demand GPUs. Use when deploying or serving AI/ML models, running GPU-accelerated workloads (training, fine-tuning, inference), serving web endpoints, scheduling batch jobs, or scaling Python code to cloud containers with the Modal SDK.
uptime-monitor
Monitor website uptime - check availability, response times, and status.
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.
craft-cloud
Craft Cloud — Pixel & Tonic's serverless hosting platform for Craft CMS. Covers craft-cloud.yaml configuration, the Build → Migrate → Release deploy pipeline, the craftcms/cloud extension package, edge image transforms via Cloudflare, edge static caching with cache.rules + ESI, Cloud-managed S3 filesystem, MySQL 8 /…