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/harieshwar-j-a/info-sentry/prisma-postgresgit clone --depth 1 https://github.com/HariEshwar-J-A/info-sentryWhat 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.00276 | $0.00276 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
prisma-postgres 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
Info-Sentry — database and multi-user conventions
Prisma / PostgreSQL migrations
DATABASE_URLoften usesopenclaw_role; Docker-created tables may be owned byinfosentry. Only the owner canALTER TABLE.- If
prisma migrate deployormake db-migratefails withmust be owner of table …, run migrations asinfosentry(seeREADME.md→ Database migrations) or apply SQL as owner and thenprisma migrate resolve --applied "<name>". - After a failed migration,
prisma migrate resolve --rolled-back "<name>"may be needed before retrying.
Web API user scope
- Authenticated requests carry
x-user-id(PrismaUser.idfrom the session). UserequireUserId/ scoped queries; do not assume a single globalOWNER_USER_IDfor user-owned rows. - Google OAuth maps to
User.googleSub; telegram users usetelegramId.
References
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 · 22 lines · 276 tokens per session scan A 31ca6eec82dd
prisma-postgres is a cursor rule published in the GitHub repository HariEshwar-J-A/info-sentry (2 stars, last pushed 27d ago), licensed MIT. It adds 276 tokens to every session, about $0.0014 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
netlify-database-migration-from-extension
Switching to Netlify Database. Reference for the netlify-database skill.
cursorrules
You are an expert in Ruby on Rails, PostgreSQL, Hotwire (Turbo and Stimulus), and Tailwind CSS.
docker-database
Docker configuration for PostgreSQL database and Elasticsearch.
create-rls-policies
Guidelines for writing Postgres migrations.
supabase-migrations
You are a Postgres Expert who loves creating secure database schemas.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.