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/vepo/issues/dev-import-sql-safetygit clone --depth 1 https://github.com/vepo/issuesWhat 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.00511 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
dev-import-sql-safety 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.
What it actually says
dev-import.sql — schema change safety
dev-import.sql runs on every %dev startup via DatabaseDevSetup, after Flyway applies migrations. Any schema change must not break that script — treat migration + dev-import.sql as one deliverable.
Protected baseline
Dev personas used in tests and manual exploration:
| Asset | Why |
|---|---|
[email protected] |
Admin role, user CRUD tests |
[email protected] |
Project manager, project CRUD |
[email protected] |
Default ticket workflows |
Sample project with prefix ISS |
Kanban and ticket identifier tests |
Do not delete these users or the primary sample project without updating tests and feature-catalog.md.
When you change the schema (Flyway)
Pre-production: amend V1.0.0__Database_Creation.sql only — see issues-flyway.mdc. Do not add V1.0.x migration files.
Work through this list in the same PR as the schema change:
- Reset section — Extend TRUNCATE/DELETE in FK-safe order for tables dev seed repopulates.
- Seed section — New
NOT NULLcolumns or FKs require matching INSERT values. - Verify — Restart
mvn quarkus:devand confirmDatabaseDevSetupruns without SQL errors.
TRUNCATE CASCADE trap
PostgreSQL TRUNCATE parent CASCADE truncates every table with an FK to parent. Clear inbound FKs first, then delete children; never assume CASCADE stops at intended tables.
Quick checklist
- Reset section covers new dev-populated tables
- Inserts satisfy new NOT NULL and FK constraints
- Protected dev personas still exist after reset
-
%devstartup completes withdev-import.sqlexecuting successfully
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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A 338b33c62282
dev-import-sql-safety is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 511 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-31.
Other cursor rules, from other repositories
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
com-example-service-PublicPaymentController
AI rules for com.example.service.PublicPaymentController.
front-vue-page-conventions
YiSmartCloud front-end Vue page conventions.
cursorrules
Cursor rule "cursorrules" from Forge-Space/ui-mcp, covering uiforge mcp cursor rules, environment setup, development guidelines, component library integration and figma integration.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.