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.
git clone --depth 1 https://github.com/netlify/context-and-toolsWrote 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/rules/netlify/context-and-tools/netlify-frameworks-astro)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-frameworks-astro"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-frameworks-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/rules/netlify/context-and-tools/netlify-frameworks-astro"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-frameworks-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.00015 | $0.01163 |
| Opus 5.5 | $0.00006 | $0.00465 |
| Sonnet 5.5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
netlify-frameworks-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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro on Netlify
Setup
Check current versions before pinning. Knowledge cutoffs lag behind npm, and guessing a version tends to fail (
npm installrejects it, or worse, installs something incompatible). Before pinning@astrojs/netlify,astro, or any other package inpackage.json, runnpm view <pkg> versionto get the currentlatest. Or omit explicit pins and letnpm installpick them up. If that check itself fails (no network, registry unreachable), still don't fall back to a guessed exact pin — install without a version (or with@latest) and tell the user live verification wasn't possible so they should confirm the installed versions. Never present an unverifiedx.y.zas the current release.
Install the Netlify adapter:
npx astro add netlify
This installs @astrojs/netlify and updates astro.config.* automatically.
Manual Setup
npm install @astrojs/netlify
// astro.config.mjs
import { defineConfig } from "astro/config";
import netlify from "@astrojs/netlify";
export default defineConfig({
output: "server", // on-demand (SSR) by default; or "static" (the default) for prerendered
adapter: netlify(),
});
Output Modes
Astro 5 removed the "hybrid" mode — there are now two output modes, and per-route control replaces it. Both modes need the adapter once any route renders on demand.
| Mode | Behavior |
|---|---|
"static" (default) |
Prerendered (hybrid-by-default): pages are static HTML at build time. Opt individual routes into on-demand rendering with export const prerender = false. |
"server" |
On-demand (SSR) by default. Opt individual routes into prerendering with export const prerender = true. |
What the Adapter Does
- Converts Astro server routes into Netlify Functions
- Handles SSR, API routes, and middleware
- Maps Astro's routing to Netlify's function routing
- You do not write raw Netlify Functions for Astro's server routes
API Routes
Astro API routes (in src/pages/api/) are handled by the adapter:
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 · 131 lines · 15 tokens per session scan A 41110b752f9b
netlify-frameworks-astro is a cursor rule published in the GitHub repository netlify/context-and-tools (41 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,163 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 cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.