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/janhesters/react-router-saas-template/facadesgit clone --depth 1 https://github.com/janhesters/react-router-saas-templateWrote 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/janhesters/react-router-saas-template/facades)<a href="https://agentmods.dev/rules/janhesters/react-router-saas-template/facades"><img src="https://agentmods.dev/badge/rules/janhesters/react-router-saas-template/facades.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.00289 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
facades 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 4d 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
Facade Functions
FacadeConstraints {
- Apply only to functions in
*-model.tsfiles. - Function names must follow
<action><Entity><OptionalWith...><DataSource><OptionalBy...>()pattern. - Allowed actions: save | retrieve | update | delete.
- Entity names are singular, in PascalCase.
- Use “With…” to indicate included relations before “From/In/ToDatabase”.
- Use “By…” to indicate lookup key(s) last; key names must match schema fields exactly.
- Use “And” to chain multiple included relations or keys.
- Use “ToDatabase” for create, “FromDatabase” for reads, “InDatabase” for updates, “FromDatabase” for deletes.
- Facades must perform a single database operation (no business logic).
- Facades must always return raw Prisma results (no transformations).
- Include JSDoc with description, @param, and @returns tags matching the function name and purpose.
- Prefer explicit Prisma includes/selects; avoid
include: { *: true }. - Function bodies must use the
prisma.<entity>.<operation>pattern directly. }
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.
- 4d ago First seen · 24 lines · 289 tokens per session scan A 23a6ad000c66
facades is a cursor rule published in the GitHub repository janhesters/react-router-saas-template (48 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 289 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
cursorrules
You are an expert in SQL and Tinybird. Follow these instructions when working with .datasource and .pipe files.
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.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.