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 commands/openshift-online/agent-control-plane/trex.db.setupgit clone --depth 1 https://github.com/openshift-online/agent-control-planeWhat 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.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
trex.db.setup 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 3d 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.
This is a copy
100% identical to trex.db.setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Set Up Database
Start a fresh PostgreSQL container and run all migrations. If a database already exists, this will tear it down first.
Instructions
-
Check if a PostgreSQL container is already running:
docker ps -a --filter name=ambient-api-server-postgres --format "{{.Names}} {{.Status}}" -
If a container exists, tear it down first:
make db/teardown -
Start a fresh PostgreSQL container:
make db/setup -
Wait for PostgreSQL to be ready:
sleep 2 -
Build the binary if not already built:
make binary -
Run migrations:
./ambient-api-server migrate
When to Use This
- First-time database setup
- After generating a new Kind (new migration added)
- After pulling changes that include new migrations
- When integration tests fail with "relation does not exist" or column errors
- When the database schema is corrupted or out of sync
Database Connection Details
Connection details are stored in the secrets/ directory files (db.host, db.port, db.name, db.user, db.password).
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.
- 3d ago First seen · 48 lines · 0 tokens per session scan A 84cbfea7d230
trex.db.setup is a command published in the GitHub repository openshift-online/agent-control-plane (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 tokens. A static security scan graded it A with 0 findings. It is 100% identical to trex.db.setup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
pgai:issues
Work with PostgresAI Issues from console.postgres.ai.
db
Set up or operate Supabase Postgres for this project.
new-database
Command "new-database" from mitchross/talos-argocd-proxmox, covering default path: plain postgres + kopiur (since 2026-07-09), steps, critical rules, what about pitr / cnpg? and reference.
database
You MUST start your FIRST response with this exact agent activation line.
schema-designer
Design normalized Postgres/Supabase schemas — tables, columns, types, keys, indexes, and constraints with consistent naming. Use when creating a new database...