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/squirrelogic/cursor-rules/naming-conventionsgit clone --depth 1 https://github.com/squirrelogic/cursor-rulesWrote 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/squirrelogic/cursor-rules/naming-conventions)<a href="https://agentmods.dev/rules/squirrelogic/cursor-rules/naming-conventions"><img src="https://agentmods.dev/badge/rules/squirrelogic/cursor-rules/naming-conventions.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.00000 | $0.00473 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
naming-conventions 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- naming-conventions — 100% identical, 0 lines differ
What it actually says
Naming Conventions
Standards for naming TypeScript and JavaScript files, types, and functions.
actions:
-
type: reject conditions:
Reject files not in kebab-case
- pattern: "^(?!.[A-Z])(?!.\s)(?!.*_)[a-z0-9-]+\.(ts|js)$" message: "File names must be in kebab-case (e.g., my-file-name.ts)"
-
type: suggest message: | Follow these naming conventions:
-
Files:
- Use kebab-case for all TypeScript and JavaScript files
- Examples: ✅ user-service.ts ✅ api-client.js ❌ UserService.ts ❌ apiClient.js
-
Types (interfaces, types, classes):
- Use PascalCase
- Examples: ✅ interface UserProfile ✅ type ApiResponse ✅ class HttpClient ❌ interface userProfile ❌ type api_response
-
Functions:
- Use camelCase
- Examples: ✅ function getUserData() ✅ const fetchApiResponse = () => {} ❌ function GetUserData() ❌ const fetch_api_response = () => {}
-
examples:
-
input: | // Bad: Incorrect naming UserService.ts API_client.js
interface user_profile {} function FetchData() {}
// Good: Correct naming user-service.ts api-client.js
interface UserProfile {} function fetchData() {} output: "Correctly named files, types, and functions"
metadata: priority: high version: 1.0
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.
- 3d ago First seen · 76 lines · 473 tokens per session scan A 99860508f1da
naming-conventions is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 473 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.