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/ambient-code/platform/trex.test.integrationgit clone --depth 1 https://github.com/ambient-code/platformWhat 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.00282 |
| Opus 5 | $0.00000 | $0.00141 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
trex.test.integration 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- trex.test.integration — 100% identical, 0 lines differ
What it actually says
Run Integration Tests
Run integration tests against a real PostgreSQL database (provisioned automatically via testcontainers).
Instructions
-
Build the binary to ensure everything compiles:
make binary -
Run integration tests:
make test-integration -
To run a specific test or subset:
TESTFLAGS="-run TestDinosaurGet" make test-integration -
Report results with pass/fail summary.
How Integration Tests Work
- Database: Testcontainers automatically starts a PostgreSQL instance (no manual setup needed)
- Each test calls
test.RegisterIntegration(t)which returns a(*Helper, *openapi.APIClient) - The database is reset between tests via
helper.DBFactory.ResetDB() - Tests use gomega matchers (
Expect(...).To(...))
Test Files
test/integration/— Contains all integration test files
Adding New Test Files
Follow the pattern in existing test files. Every test function should:
- Call
h, client := test.RegisterIntegration(t) - Create an account:
account := h.NewRandAccount() - Get an authenticated context:
ctx := h.NewAuthenticatedContext(account) - Use
client.DefaultAPI.Api...methods for API calls
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.
- yesterday First seen · 42 lines · 0 tokens per session scan A 1cfabfcc986f
trex.test.integration is a command published in the GitHub repository ambient-code/platform (129 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 282 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 commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
proposal
Create a structured feature proposal in docs/11-proposals/.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
doctor
Run procedural readiness checks for goal-flight.