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 skills add litestar-org/litestar-skills --skill pytest-databasesgit clone --depth 1 https://github.com/litestar-org/litestar-skillsWrote 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/skills/litestar-org/litestar-skills/pytest-databases)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/pytest-databases"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/pytest-databases/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/skills/litestar-org/litestar-skills/pytest-databases"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/pytest-databases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.02008 |
| Opus 5.5 | $0.00028 | $0.00803 |
| Sonnet 5.5 | $0.00014 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
pytest-databases 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 4d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pytest-databases
pytest-databases provides session-scoped, container-backed service fixtures.
This guidance targets the immutable v0.19.0 tag. Load only the plugin modules
the test suite uses. Consume a ready client fixture where one exists; otherwise
connect with the client already used by the project.
Code Style Rules
- Keep database I/O consistent with the project driver. The package's
PostgreSQL connection fixtures use synchronous
psycopg; do notawaittheir methods. - Type service fixtures with the service class from the same plugin module.
- Prefer ready client fixtures when provided. For service-only plugins, build the project's existing client from the service object's host, port, and credentials.
- Keep plugin declarations in the nearest
conftest.py; do not load every backend globally.
Quick Reference
Install and enable
pip install "pytest-databases[postgres]"
In conftest.py:
pytest_plugins = ["pytest_databases.docker.postgres"]
The core pytest_databases pytest entry point supplies docker_client and
docker_service. Each database module supplies its own fixtures.
Choose the fixture shape
| Need | Use |
|---|---|
A ready psycopg connection |
postgres_connection, a versioned PostgreSQL-family connection, or cockroachdb_connection |
| A ready vendor client | bigquery_client, spanner_connection, mongodb_connection, an Oracle connection, a GizmoSQL connection, or an Azure Blob container client |
| Service coordinates for the project's own client | The backend's *_service fixture |
| A specific PostgreSQL-family release | Matching *_NN_service, *_NN_connection, and *_NN_port fixtures |
| Parallel worker isolation | The backend's exact *_xdist_isolation_level fixture from xdist.md |
See reference.md for the exact plugin, service, and
ready-client matrix. Do not infer a *_connection fixture from a
*_service fixture's name.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +1 lines 5810c9b90fd2
- 20d ago Changed · +8 lines 4845d477378d
- 28d ago Changed · +8 lines · -10 tokens per session 17236a56d05c
- 1mo ago First seen · 176 lines · 79 tokens per session scan A 2d5d94f7ab3b
pytest-databases is a skill published in the GitHub repository litestar-org/litestar-skills (16 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 2,008 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ecto-patterns
Use when a task touches Ecto, even a how-to question: schemas, changesets, validations, queries, preloads, Multi, migrations, constraints, money fields. Load it before writing Ecto code. Skip for Ash.
ecto-constraint-debug
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing uniqueconstraint, foreignkeyconstraint, or checkconstraint errors.
cargo-pgrx
Choose and run cargo-pgrx commands, pgrx tests, pgtest coverage, and pgsys boundary checks.
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
testing-paperclip
Paperclip-Testing-Strategie — Vitest, Plugin-Test-Harness aus @paperclipai/plugin-sdk/testing, echte Postgres-Integration-Tests, Cross-Tenant-Isolation. Verwenden Sie dies beim Schreiben oder Reviewen von Paperclip-Tests.
wicked-garden-qe-data-quality-tester
Data-quality specialist — schema drift, referential integrity, migration forward/rollback verification, greatexpectations / dbt-test patterns. Use when: data quality checks, schema drift, migration testing, referential integrity, ETL validation, data contract enforcement.