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/tholem-ai/tholem-cursor-kit/050-project-constraintsgit clone --depth 1 https://github.com/Tholem-AI/Tholem-Cursor-KitWrote 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/tholem-ai/tholem-cursor-kit/050-project-constraints)<a href="https://agentmods.dev/rules/tholem-ai/tholem-cursor-kit/050-project-constraints"><img src="https://agentmods.dev/badge/rules/tholem-ai/tholem-cursor-kit/050-project-constraints.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.1 | $0.00237 | $0.00237 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
050-project-constraints 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 5d 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
050-project-constraints
Purpose
Define project-level technical constraints while keeping stack decisions requirements-driven and review-gated.
Mandatory policy
- Do not change core stack, framework, or architecture without explicit user approval.
- Treat stack/version constraints as inferred project context, not fixed template defaults.
- Use this stack inference order:
- requirements/design artifacts,
- detected project config files,
- conservative fallback assumptions (explicitly labeled).
- Present inferred stack constraints in a reviewable plan/diff before applying.
- Treat
docs/Project-Constraints.mdas the canonical project-constraints documentation surface and keep it aligned with runtime decisions. - Do not treat fallback versions as mandatory policy targets.
Integration points
- Governance authority:
.cursor/rules/010-governance.mdc - Execution lifecycle:
.cursor/rules/020-execution.mdc - Safety constraints:
.cursor/rules/030-safety.mdc - Validation gates:
.cursor/rules/040-quality.mdc
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.
- 5d ago First seen · 33 lines · 237 tokens per session scan A 6ee730a5b8ec
050-project-constraints is a cursor rule published in the GitHub repository Tholem-AI/Tholem-Cursor-Kit (4 stars, last pushed 3mo ago), licensed MIT. It adds 237 tokens to every session, about $0.0012 per session on Opus 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.
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.