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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/astro)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/astro"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/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/nedcodes-ok/cursorrules-collection/astro"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/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.00408 | $0.00408 |
| Opus 5.5 | $0.00163 | $0.00163 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
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 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.
What it actually says
Astro Cursor Rules
You are an expert Astro developer. Follow these rules:
Architecture
- Server-first: default to zero client JS. Add islands only for interactivity
- Content collections with Zod schemas for all structured content
- File-based routing in src/pages/. Dynamic routes with [...slug].astro
- Layouts in src/layouts/, reusable components in src/components/
Islands Architecture
- client:load only for immediately interactive components (nav menus, forms)
- client:visible for below-fold interactive content (comments, carousels)
- client:idle for non-critical interactivity (analytics widgets)
- client:media for responsive islands (mobile-only menus)
- Never client:load what could be client:visible
Content
- Define collections in src/content/config.ts with strict Zod schemas
- Use getCollection() and getEntry() — never raw file imports
- MDX for content that needs components. Markdown for everything else
- Frontmatter validation catches errors at build time — use it
Performance
- Static generation (SSG) by default. SSR only for personalized/dynamic pages
- Image component for all images — automatic format/size optimization
- Inline critical CSS. Astro does this automatically — dont fight it
- Prefetch visible links with data-astro-prefetch
Styling
- Scoped styles in tags — they are component-scoped by default
- Use :global() sparingly and only in layouts
- CSS custom properties for theming over CSS-in-JS
- No Tailwind classes in .astro files unless project-wide decision
Data Fetching
- Fetch in frontmatter (server-side) — runs at build time for SSG
- API routes in src/pages/api/ for dynamic endpoints
- Use Astro.response for setting headers/status in SSR
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 · 46 lines · 408 tokens per session scan A 1b752df3fb35
astro is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 408 tokens to every session, about $0.0016 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
auto-update-llms-robots-txt
Auto-update llms.txt and robots.txt when pages are created or edited.
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
09-android-best-practices
Android engineering best practices.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.