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/maccman/ai-expo-starter-template/code-conventionsgit clone --depth 1 https://github.com/maccman/ai-expo-starter-templateWhat 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.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
code-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 2d 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
Code Conventions
When writing or modifying code in this project, please adhere to the following conventions:
- TypeScript Best Practices: Follow standard, idiomatic TypeScript coding practices for structure, naming, and types, unless otherwise overridden.
- Minimal Comments: Avoid adding comments unless they explain complex logic or non-obvious decisions. Well-written, self-explanatory code is preferred. Do not add comments that merely restate what the code does.
- Tests as Documentation: Rely on comprehensive tests (which will be added later if not present) to document the behavior and usage of the code, rather than extensive comments within the code itself.
- File naming conventions: Use kebab-case when naming directories, TypeScript, and other files.
- Type checking: after major modifications run
pnpm typecheckand fix any errors. - UX/UI We are using Tailwind CSS, React, shadcn/ui components and Lucide React icons. Generate responsive designs. Provide default props for React Components. Check to see if a shadcn component exists under
components/uibefore installing it. - Models/db/tables When pulling in a database type, Kysely.
- Open-source conventions Pretend you are writing code for a open-source project. Write best-in-class code.
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.
- 2d ago First seen · 19 lines · 312 tokens per session scan A f664773428d8
code-conventions is a cursor rule published in the GitHub repository maccman/ai-expo-starter-template (4 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 312 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
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.