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/gurbaaz27/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/gurbaaz27/cursorrules/auto-update-llms-robots-txt.mini)<a href="https://agentmods.dev/rules/gurbaaz27/cursorrules/auto-update-llms-robots-txt.mini"><img src="https://agentmods.dev/badge/rules/gurbaaz27/cursorrules/auto-update-llms-robots-txt.mini.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.1 | $0.00000 | $0.00251 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
auto-update-llms-robots-txt.mini 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 7d 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
Auto-Update llms.txt & robots.txt
Update llms.txt and robots.txt when pages are created/edited to reflect the current state of all crawlable pages.
Quick Rules
Protected routes (Disallow):
- Paths:
/admin/,/dashboard/,/account/,/auth/,/api/ - Code:
useAuth,withAuth,getSession,middleware.ts - Folders:
(protected),(auth),private/
Public routes (Allow):
- No auth logic
- Common:
/,/about,/blog/*,/docs/*,/pricing
Output
After changes, update both files and report:
- New/modified routes
- Public vs protected count
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.
- 7d ago First seen · 34 lines · 0 tokens per session scan A 713971241d39
auto-update-llms-robots-txt.mini is a cursor rule published in the GitHub repository gurbaaz27/cursorrules (1 stars, last pushed 8mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 251 tokens. 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-31.
Other cursor rules, from other repositories
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.