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/patrickjs/awesome-cursorrules/astro-typescript-cursorrules-prompt-filegit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/astro-typescript-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/astro-typescript-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/astro-typescript-cursorrules-prompt-file.svg" alt="Measured on agentmods" 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 | $0.00536 | $0.00536 |
| Opus 5 | $0.00268 | $0.00268 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
astro-typescript-cursorrules-prompt-file 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 4d 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
{ "rules": { "commit_message_guidelines": { "description": "Guidelines for creating conventional commit messages.",
"format": {
"description": "The format for commit messages using the conventional commits spec.",
"body": "[optional scope]: \n\n[optional body]\n\n[optional footer(s)]"
},
"enabled": true,
"rules": [
{
"description": "Always suggest a conventional commit with a type and optional scope in lowercase letters."
},
{
"description": "Keep the commit message concise and within 60 characters."
},
{
"description": "Ensure the commit message is ready to be pasted into the terminal without further editing."
},
{
"description": "Provide the full command to commit, not just the message."
}
],
"examples": [
{
"prompt": "<diff_context> /commit",
"response": "git commit -m 'feat: add responsive navbar with TailwindCSS'"
}
]
},
"development_guidelines": {
"description": "Guidelines for developing code with Astro, TypeScript, and TailwindCSS.",
"enabled": true,
"rules": [
{
"description": "Enforce strict TypeScript settings, ensuring type safety across the project."
},
{
"description": "Use TailwindCSS for all styling, keeping the utility-first approach in mind."
},
{
"description": "Ensure Astro components are modular, reusable, and maintain a clear separation of concerns."
}
]
},
"coding_style": {
"description": "Guidelines for maintaining consistent coding style.",
"enabled": true,
"rules": [
{
"description": "Code must start with path/filename as a one-line comment."
},
{
"description": "Comments should describe purpose, not effect."
},
{
"description": "Prioritize modularity, DRY principles, and performance."
}
]
},
"custom_slash_commands": {
"description": "Custom slash commands.",
"enabled": true,
"commands": [
{
"name": "/commit",
"description": "Generate a Git commit message using the conventional commits spec.",
"enabled": true
}
]
}
} }
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.
- 4d ago First seen · 92 lines · 0 tokens per session scan A 293984a4287a
astro-typescript-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,717 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 536 tokens to every session, about $0.0027 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-30.
Other cursor rules, from other repositories
snyk_rules
Snyk Security At Inception.
cursorrules
// Good: Use anyhow for application errors use anyhow::{Context, Result}.
project
Project rules for application source, tests, and documentation.
nextjs
Next.js: App Router, Server Components, server actions.
go
Go patterns: error wrapping, goroutines, interfaces.
code-review
Code review: reviewing approach, authoring PRs, feedback conventions.