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.verifygit clone --depth 1 https://github.com/openshift-online/agent-control-planeWrote 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/commands/openshift-online/agent-control-plane/trex.verify)<a href="https://agentmods.dev/commands/openshift-online/agent-control-plane/trex.verify"><img src="https://agentmods.dev/badge/commands/openshift-online/agent-control-plane/trex.verify.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00250 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
trex.verify 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.
This is a copy
100% identical to trex.verify — 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
Verify Code Quality
Run all static analysis checks: go vet, format verification, and linting.
Instructions
Step 1: Run Verification
make verify
This runs:
go vet ./cmd/... ./pkg/... ./test/...— checks for suspicious constructsgofmtformatting check — warns if any files are not properly formatted
Step 2: Run Linter
make lint
This runs golangci-lint against the codebase (ignores unused warnings).
Step 3: Fix Issues
- Formatting issues: Run
gofmt -w .to auto-fix - Vet errors: These indicate real bugs (unreachable code, incorrect printf args, etc.) — fix manually
- Lint warnings: Address based on severity; some may be intentional
Step 4: Build Confirmation
make binary
When to Run This
- Before committing changes
- After generating a new Kind
- As part of a CI-like local check before pushing
- When the user asks to "clean up" or "check the code"
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 First seen · 43 lines · 0 tokens per session scan A b2d4e3fa7c1c
trex.verify is a command published in the GitHub repository openshift-online/agent-control-plane (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 tokens. A static security scan graded it A with 0 findings. It is 100% identical to trex.verify, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
research
Research a technical or product question.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.