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 rules/toptalentcoder/cursor-awesomerules/astro-development-guidelinesgit clone --depth 1 https://github.com/toptalentcoder/Cursor-AwesomeRulesWhat 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.00079 | $0.00079 |
| Opus 5 | $0.00039 | $0.00039 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
astro-development-guidelines 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 2d 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.
This is a copy
100% identical to astro-development-guidelines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Enforces specific development guidelines for Astro projects, including TypeScript strictness and TailwindCSS usage. globs: *.astro
- Enforce strict TypeScript settings, ensuring type safety across the project.
- Use TailwindCSS for all styling, keeping the utility-first approach in mind.
- Ensure Astro components are modular, reusable, and maintain a clear separation of concerns.
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.
- 2d ago First seen · 7 lines · 79 tokens per session scan A 452eee429810
astro-development-guidelines is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 79 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to astro-development-guidelines, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
astro-typescript-cursorrules-prompt-file
Cursor rules for Astro development with TypeScript integration.
no-magic-numbers
Prefer named constants over unexplained numeric literals in TypeScript. Apply when editing .ts/.tsx behavior code.
use-bun-instead-of-node-vite-npm-pnpm
Use Bun instead of Node.js, npm, bun, or vite.
svelte-typescript
Svelte 5 and TypeScript patterns for Keymoji components and stores.
coding-standards
Coding standards and formatting conventions.
astro-development-guidelines
Enforces specific development guidelines for Astro projects, including TypeScript strictness and TailwindCSS usage.