db-reset-coordination

db-reset-coordination is a cursor rule for Cursor from YuDefine/nuxt-supabase-starter. It costs 266 tokens per session, scanned A, original, MIT.

A safety rule for resetting a development database when several linked checkouts may depend on it. It requires those peers to coordinate before the reset is allowed.

In plain words
What is it for?
It is for coordinating database resets across shared worktrees and development environments.
Why use it?
It prevents one developer or agent from resetting data while another checkout is still using it.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions Codex.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/db-reset-peer-coordination.ts coordinate --cwd "$(pwd)".

Good fit It is for coordinating database resets across shared worktrees and development environments.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starter
agentmods
npx agentmods add rules/yudefine/nuxt-supabase-starter/db-reset-coordination

Made for: Cursor.

Wrote 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.

agentmods badge for db-reset-coordination

README.md
[![agentmods](https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/db-reset-coordination/github.svg)](https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/db-reset-coordination)
Your own site
<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/db-reset-coordination"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/db-reset-coordination/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.

agentmods 80×15 button for db-reset-coordination

Your own site · 80×15
<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/db-reset-coordination"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/db-reset-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 266 This file is loaded in full into every session.
When invoked 266 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00266 $0.00266
Opus 5 $0.00133 $0.00133
Sonnet 5 $0.00053 $0.00053
Haiku 4.5 $0.00027 $0.00027

Measured 2d ago against content hash 5b936a0cf752, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

db-reset-coordination 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.

template/.cursor/rules/db-reset-coordination.mdc · 25 lines

What it actually says

DB Reset Coordination

每一次從 primary checkout reset dev DB 前,MUST 先跑:

node scripts/db-reset-peer-coordination.ts coordinate --cwd "$(pwd)"

只有 safe_to_reset 才可 reset。Helper 以 git common-dir 找同專案 Herdr peers;resettingdependent peer 完成或到 checkpoint 後 release,requester 最後 reset。

Iron Law:未收斂就不 reset;warning、title、idledone 都不是同意。 缺回覆、Herdr 不可用、identity/correlation mismatch、timeout 均 fail closed;agent MUST 自行協調,NEVER 照跑或叫 user 排序。

Linked worktree 回 not_applicable 後走 DB topology rule;shared/canonical DB 另須 db-lease。Herdr NEVER 傳 secret、credential 或 DB row data。

Changes

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.

  1. 2d ago Changed · +1 lines · +14 tokens per session 5b936a0cf752
  2. 6d ago First seen · 24 lines · 252 tokens per session scan A ea23cbd2d762

Subscribe to this mod's changes

db-reset-coordination is a cursor rule published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed yesterday), licensed MIT. It adds 266 tokens to every session, about $0.0013 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-09-03.