pREST is an API service that creates REST and Model Context Protocol endpoints for an existing or new PostgreSQL database, covering database operations, custom SQL routes, authentication, access control, and read-only MCP access. Developers use it to expose PostgreSQL data without writing a separate backend. The catalogue entries provide rules, skills, and instructions for using pREST.
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/prest/prestWrote 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/prest/prest/integration-tests)<a href="https://agentmods.dev/rules/prest/prest/integration-tests"><img src="https://agentmods.dev/badge/rules/prest/prest/integration-tests/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/prest/prest/integration-tests"><img src="https://agentmods.dev/badge/rules/prest/prest/integration-tests.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.00000 | $0.00601 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
integration-tests 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Tests
Integration tests must be human-readable. A reader should understand scenario, expected outcome, and why each request matters without decoding URLs alone.
Document every request
- Sequential: before each HTTP call, 1–3 comments: What / Expected outcome / Why (if non-obvious)
- Table-driven: clear
descriptionper case (scenario + expected outcome); use int.Run/t.Log - Prefer wrapping long
DoRequest/DoAuthRequestacross lines; stable scenario name arg
Helpers (do / don't)
| Do | Don't |
|---|---|
helpers.ServerURL, QueriesServerURL, AuthServerURL, MultiClusterServerURL |
httptest.NewServer for standard controller routes |
testutils.DoRequest / helpers.DoAuthRequest |
postgres.Load() or live DB outside integration/ |
Placement
- Wire-compatible HTTP E2E →
integration/suites/(Postgres job owns these) - Engine- or stack-specific →
integration/<db>/(e.g.postgres/,timescaledb/)
Templates and gold-file walkthrough: skill prest-integration-tests (+ examples.md).
Layout/CI contract: integration-layout.mdc.
MUST: every application behavior change ships with an integration test
A unit test with mocks proves a code path can be reached and returns the
right value in isolation; only an integration test proves it is reached
through real HTTP routing and behaves correctly end-to-end. Unit coverage
(unit-tests-tdd.mdc) is necessary but not sufficient — do not consider a
behavior change (controller, adapter, middleware, query-param parsing, SQL
building, etc.) done without a paired integration test in integration/suites/
or integration/<db>/.
Precedent: _select's SQL-injection fix (GHSA-qvx3-q8vx-9q3c) landed with
unit coverage for its own validator (sanitizeSelectField). The sibling
_groupby path used a separate, weaker validator (isSafeSQLExpression) that
no integration test ever exercised end-to-end — the gap went unnoticed until a
dedicated audit found it. Unit tests alone did not — and structurally could
not — catch a sibling code path being missed entirely; only an HTTP-level
test asserting the actual response for both _select and _groupby would
have. See integration/suites/controllers/crud_test.go (_groupby subquery/UNION injection cases) for the test that now guards it.
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 · 52 lines · 0 tokens per session scan A 21c8d99c799d
integration-tests is a cursor rule published in the GitHub repository prest/prest (4,623 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 601 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-30.
Other cursor rules, from other repositories
test-database-limitations
Test databases created via withDevDatabase() from @repo/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.
sql-orm-client-whole-shape-assertions
Prefer whole-result-shape assertions with explicit select projections in sql-orm-client tests.
go-service-errors
Go service error translation, nullable TIMESTAMPTZ scans, history, and side effects.
database-interaction-best-practices
Best practices when interacting with databases in backend Go code.
test-database-limitations
Test databases created via withDevDatabase() from @prisma-next/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.