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/toptalentcoder/Cursor-AwesomeRulesWrote 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/toptalentcoder/cursor-awesomerules/convex-schema-design-built-in-types)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/convex-schema-design-built-in-types"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/convex-schema-design-built-in-types/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/toptalentcoder/cursor-awesomerules/convex-schema-design-built-in-types"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/convex-schema-design-built-in-types.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.00097 | $0.00097 |
| Opus 5 | $0.00048 | $0.00048 |
| Sonnet 5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
convex-schema-design---built-in-types 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 9d 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.
This is a copy
100% identical to convex-schema-design---built-in-types — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- When designing the schema, refer to the built-in System fields and data types available at https://docs.convex.dev/database/types.
- Pay special attention to the correct usage of the
vvalidator builder (https://docs.convex.dev/api/modules/values#v) for defining schema types.
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.
- 9d ago First seen · 6 lines · 97 tokens per session scan A af8f3ea0160f
convex-schema-design---built-in-types is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 97 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to convex-schema-design---built-in-types, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
query-optimization
A database performance rule that requires measuring PostgreSQL queries with EXPLAIN ANALYZE under the same user permissions and row-level security (RLS) conditions used in production.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.