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/vepo/issuesWrote 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/vepo/issues/issues-flyway)<a href="https://agentmods.dev/rules/vepo/issues/issues-flyway"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-flyway/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/vepo/issues/issues-flyway"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-flyway.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.00409 | $0.00409 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
issues-flyway 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
Flyway — pre-production schema changes
Issues is not in production yet (AGENTS.md). There are no deployed databases to migrate incrementally.
Rule
| Situation | Action |
|---|---|
| New/changed table or column | Edit V1.0.0__Database_Creation.sql |
| Pre-production (now) | Do not add V1.0.1__…, V1.1__…, or other versioned migration files |
| After first production deploy | Switch to incremental Flyway versions; do not rewrite shipped migrations |
Same PR checklist
- Update
V1.0.0__Database_Creation.sql(CREATE/ALTER in baseline script). - Update
dev-import.sqlif seed data needs new NOT NULL columns or FKs — see dev-import-sql-safety.mdc. - Update JPA entities to match.
- Run
mvn test(Flyway runs on@QuarkusTeststartup).
Examples
-- ✅ Pre-production: add column to CREATE TABLE in V1.0.0
CREATE TABLE tb_projects (
...
ticket_template_enabled BOOLEAN NOT NULL DEFAULT FALSE,
...
);
-- ❌ Pre-production: separate migration file
-- V1.0.1__Add_Ticket_Template.sql
ALTER TABLE tb_projects ADD COLUMN ...
Never
- Bypass Flyway — schema still lives under
src/main/resources/db/migration/. - Add a new migration version while the project remains pre-production (unless the user explicitly requests production rollout prep).
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 · 44 lines · 409 tokens per session scan A eea7799f7ae5
issues-flyway is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 409 tokens to every session, about $0.0016 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
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
pages
Source: docs/agents/pages.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.
postgresql
A set of rules for working with PostgreSQL, a relational database that stores organised data in tables linked by defined relationships.
firebase
Best practices for Firebase integration including Authentication, Firestore, Storage, and Functions.