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.unitgit 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.00152 |
| Opus 5 | $0.00000 | $0.00076 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
trex.test.unit 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- trex.test.unit — 100% identical, 0 lines differ
What it actually says
Run Unit Tests
Run unit tests against the package and command code (no database required).
Instructions
-
Run unit tests:
make test -
To run specific tests:
TESTFLAGS="-run TestLoadServices" make test -
Report results with pass/fail summary.
How Unit Tests Work
- Scope:
./pkg/...and./cmd/... - Uses standard
go testfor output
When to Use This vs trex.test.integration
- Unit tests: Fast, no external dependencies, test individual packages
- Integration tests: Full stack with real database, test API endpoints end-to-end
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 · 28 lines · 0 tokens per session scan A c7585ca338a8
trex.test.unit 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 152 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.