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/BetterTyped/hype-stackWrote 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/bettertyped/hype-stack/backend-deletion-cascades)<a href="https://agentmods.dev/rules/bettertyped/hype-stack/backend-deletion-cascades"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/backend-deletion-cascades/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/bettertyped/hype-stack/backend-deletion-cascades"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/backend-deletion-cascades.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.00020 | $0.00217 |
| Opus 5.5 | $0.00008 | $0.00087 |
| Sonnet 5.5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
backend-deletion-cascades 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
Backend Deletion Cascades
When removing a backend domain entity, delete all of its owned dependencies as part of the same mutation.
- Perform dependent deletes in a single database transaction.
- Keep delete logic in the relevant
db/mutationsfunction. - Delete child records before the parent record when database constraints require it.
- Do not leave placeholder delete mutations that only return the removed entity ID.
Example:
import { postgres } from "@backend/context";
export const deleteProjectMutation = async ({
projectId,
}: {
projectId: string;
}) => {
await postgres.qb.transaction().execute(async (trx) => {
await trx
.deleteFrom("document")
.where("projectId", "=", projectId)
.execute();
await trx.deleteFrom("project").where("id", "=", projectId).execute();
});
return { projectId };
};
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 · 20 tokens per session scan A 4049aab327d2
backend-deletion-cascades is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 217 once invoked, about $0.0001 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
backend-architecture
The backend is built on Supabase, providing PostgreSQL database, authentication, and Edge Functions for serverless API endpoints.
server-actions
Server Action, service and tenancy contract.
payload-configuration
Shipkit conditionally initializes Payload CMS based on environment variables. The src/payload.config.ts file handles graceful degradation when no database is configured.
graceful-degradation
Shipkit implements graceful degradation to provide a seamless experience whether users have a database configured or not. When no DATABASEURL is provided, the application automatically falls back to local storage for data persistence.
supabase-db-create-functions
Guidelines for writing Supabase database functions.
backend
Backend development rules for TT Studio - AI model management backend.