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/Gitmaxd/ai-initWrote 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/gitmaxd/ai-init/naming_conventions)<a href="https://agentmods.dev/rules/gitmaxd/ai-init/naming_conventions"><img src="https://agentmods.dev/badge/rules/gitmaxd/ai-init/naming_conventions/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/gitmaxd/ai-init/naming_conventions"><img src="https://agentmods.dev/badge/rules/gitmaxd/ai-init/naming_conventions.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.00318 | $0.00318 |
| Opus 5.5 | $0.00127 | $0.00127 |
| Sonnet 5.5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
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 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
1. React Component Files (.tsx):
- Use PascalCase (e.g., Button.tsx, UserProfile.tsx)
2. Pages and Routes:
- Use kebab-case for page files (e.g., about-us.tsx)
- Use snake_case for dynamic route segments (e.g., [product_id].tsx)
- Use lowercase for special files (page.tsx, layout.tsx, loading.tsx)
3. Utility & Config Files (.js, .ts):
- Use kebab-case (e.g., api-helpers.ts, date-utils.ts)
4. Documentation files (.md):
- Use kebab-case (e.g., getting-started.md)
examples:
- input: "src/components/Button.tsx" output: "Valid: PascalCase for component files"
- input: "src/utils/date-helpers.ts" output: "Valid: kebab-case for utility files"
- input: "src/app/about-us/page.tsx" output: "Valid: kebab-case for routes, lowercase for special files" metadata: priority: medium version: 1.1
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 · 36 lines · 318 tokens per session scan A 5171472adda0
naming_conventions is a cursor rule published in the GitHub repository Gitmaxd/ai-init (8 stars, last pushed 1y ago), licensed MIT. It adds 318 tokens to every session, about $0.0013 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).