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/googlarz/agents-syncWrote 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/googlarz/agents-sync/cursorrules)<a href="https://agentmods.dev/rules/googlarz/agents-sync/cursorrules"><img src="https://agentmods.dev/badge/rules/googlarz/agents-sync/cursorrules/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/googlarz/agents-sync/cursorrules"><img src="https://agentmods.dev/badge/rules/googlarz/agents-sync/cursorrules.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.00241 | $0.00241 |
| Opus 5.5 | $0.00096 | $0.00096 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
cursorrules 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
.cursorrules — managed by agents-sync v1.0.0
Language: TypeScript / Next.js 14
Run tests: npm test
- Always: use kebab-case filenames (user-profile.tsx not UserProfile.tsx)
- Always: named exports only (no default exports except Next.js page/layout components)
- Always: validate external API responses with Zod
- Always: co-locate tests (Button.test.tsx next to Button.tsx)
- Always: server components by default — add 'use client' only when needed
- Always: use cn() from lib/utils.ts for conditional classNames
- Never: import PrismaClient directly (use src/lib/db.ts — connection pool exhaustion)
- Never: add /api/ routes without checking middleware.ts auth coverage
- Never: use date-fns without /utc variants (multi-timezone dashboard)
- Never: commit .env or .env.local
- Never: use TypeScript any — use unknown and narrow
- Never: push directly to main
- Never: use console.log in production (use logger utility)
- Tests: npm test
- Build: npm run build
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 · 20 lines · 241 tokens per session scan A b3fdc602edf3
cursorrules is a cursor rule published in the GitHub repository googlarz/agents-sync (5 stars, last pushed 4mo ago), licensed MIT. It adds 241 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
standard-nestjs-module-hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .
standard-back-end-typescript-clean-code-practices
This standard establishes clean code practices in TypeScript for back-end development to enhance maintainability and ensure consistent patterns across services. It covers logging best practices, error... .
standard-typescript-good-practices
Generic practices that can be applied for all TS code in our app .
standard-code-comments
When a code comment earns its place in TypeScript sources, and when the code should speak for itself .
project
Core project context for ai-context-kit.
typescript
TypeScript conventions.