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/issues-flywaygit 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.00409 | $0.00409 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 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 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
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.
- 2d 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 1mo ago), licensed Apache-2.0. It adds 409 tokens to every session, about $0.0020 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-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.