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.
git clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/trex.openapi.generate)<a href="https://agentmods.dev/commands/ambient-code/platform/trex.openapi.generate"><img src="https://agentmods.dev/badge/commands/ambient-code/platform/trex.openapi.generate/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/commands/ambient-code/platform/trex.openapi.generate"><img src="https://agentmods.dev/badge/commands/ambient-code/platform/trex.openapi.generate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00384 |
| Opus 5.5 | $0.00000 | $0.00154 |
| Sonnet 5.5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
trex.openapi.generate 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 1mo 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.openapi.generate — 100% identical, 0 lines differ
What it actually says
Regenerate OpenAPI Client Code
Regenerate the Go client code from OpenAPI specifications. Run this after modifying any openapi/*.yaml files.
Instructions
Step 1: Verify Docker/Podman is Running
The generator uses a container to run the OpenAPI code generator:
podman info --format '{{.Host.RemoteSocket.Exists}}' 2>/dev/null || docker info --format '{{.ID}}' 2>/dev/null
If neither is running, inform the user that Docker or Podman is required.
Step 2: Run the Generator
make generate
This takes 2-3 minutes. It:
- Builds a container image from
Dockerfile.openapi - Runs the OpenAPI Generator inside the container
- Copies generated Go files back into
pkg/api/openapi/
Step 3: Verify Generated Files
ls -la pkg/api/openapi/model_*.go | head -20
Check for the expected model files for each Kind defined in the OpenAPI specs.
Step 4: Build to Confirm
make binary
When to Run This
- After creating a new Kind (part of
/trex.kind.newworkflow) - After adding fields to an existing Kind's OpenAPI spec
- After modifying
openapi/openapi.yamlor anyopenapi/openapi.*.yamlfile - After resolving merge conflicts in OpenAPI specs
Troubleshooting
- "Cannot connect to Docker daemon": Start Docker/Podman first
- Build fails after generation: Check for type mismatches between your OpenAPI schema types and the presenter code
- Missing model files: Verify the schema name in
openapi.yamlmatches the$reftarget exactly
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.
- 1mo ago First seen · 53 lines · 0 tokens per session scan A 96c7313aebc5
trex.openapi.generate is a command published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 384 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
skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validador, JWT, rate limit, swag OpenAPI.
golang-backend-engineer
Build scalable Golang backend systems with Google Cloud Spanner, Pub/Sub, Redis, and Elasticsearch.
trex.openapi.generate
Regenerate the Go client code from OpenAPI specifications. Run this after modifying any openapi/.yaml files.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.