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 skills add joelbrilliant/agentic-delivery-skills --skill sandbox-to-production-gatesgit clone --depth 1 https://github.com/joelbrilliant/agentic-delivery-skillsWrote 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/skills/joelbrilliant/agentic-delivery-skills/sandbox-to-production-gates)<a href="https://agentmods.dev/skills/joelbrilliant/agentic-delivery-skills/sandbox-to-production-gates"><img src="https://agentmods.dev/badge/skills/joelbrilliant/agentic-delivery-skills/sandbox-to-production-gates/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/skills/joelbrilliant/agentic-delivery-skills/sandbox-to-production-gates"><img src="https://agentmods.dev/badge/skills/joelbrilliant/agentic-delivery-skills/sandbox-to-production-gates.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.00049 | $0.00679 |
| Opus 5.5 | $0.00020 | $0.00272 |
| Sonnet 5.5 | $0.00010 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
sandbox-to-production-gates 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sandbox to Production Gates
Overview
Use this skill when an agent wants to move work from local or sandbox into production.
The goal is simple: prove that the reviewed source, built artefact, deployed service, and live runtime are the same thing.
Green tests are not a deployment. A restart is not a deployment. A deployed bundle without smoke evidence is not a deployment.
When to Use
- Promoting sandbox work to production.
- Restarting services after config or code changes.
- Verifying a deployed UI/API after build.
- Checking whether production is running the expected commit.
- Preparing rollback before risky changes.
- Reporting production status to a user.
Promotion Gates
Gate 1: Source truth
Capture:
- repo path;
- branch;
- commit SHA;
- dirty state;
- reviewed diff surface;
- exact files intentionally included.
If there is unrelated dirty work, do not stage it. Isolate the promotion.
Gate 2: Build truth
Run the real build command for the promoted surface.
Capture:
- command;
- exit code;
- artefact path or bundle name;
- build timestamp or hash when available.
Do not claim a build passed because a dev server still runs.
Gate 3: Service truth
Identify the actual runtime service:
- service name;
- port;
- process ID;
- environment file;
- working directory;
- last restart time.
Restart only the intended service. Never restart a neighbouring prod service by matching a vague process name.
Gate 4: Runtime truth
Smoke the live runtime, not localhost in the wrong mode.
Check:
- health endpoint;
- authenticated endpoint if auth exists;
- gateway/worker connectivity if relevant;
- static asset or API version;
- key user workflow;
- logs after startup.
If a public CDN or proxy blocks automation, smoke the backend with the correct Host header and say that is what you did.
Gate 5: Rollback truth
Before promotion, know the rollback:
- previous commit;
- previous build artefact if retained;
- command to restart old version;
- config backup location;
- data migration reversibility.
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 · 126 lines · 49 tokens per session scan A 3770e1a735e7
sandbox-to-production-gates is a skill published in the GitHub repository joelbrilliant/agentic-delivery-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 679 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other skills, from other repositories
cdf-orchestration-write-dag
Use when a user describes a custom CDF Orchestration pipeline — a specific ordered combination of stages such as augmentation only, auto-labeling only, detection+captioning only, or image attribute augmentation without full auto-labeling — that no existing DAG in airflow/dags/workflows/ covers, and asks for a new…
cdf-event-video-generation
Run the CDF Orchestration Event Video Generation DAG on Kubernetes or OSMO - image-to-video anomaly generation, auto-labeling, and anomaly dataset generation. Select for requests about event video generation, anomaly video generation, image-to-video synthesis, Cosmos3 image2video, anomaly dataset creation…
cdf-image-attribute-augmentation
Run the CDF Orchestration Image Attribute Augmentation DAG on Kubernetes - person-crop clothing augmentation, attribute search, and augmented dataset generation. Select for requests about image attribute augmentation, person attribute search, person re-identification data, clothing augmentation, attribute captions…
cdf-orchestration-setup
Use when the user asks to deploy, install, reinstall, redeploy, upgrade, or connect to the CDF Orchestration Airflow controller. Owns the end-to-end deploy sequence and runs the cdf-orchestration-preflight audit first. Covers make setup, controller image builds, Helm installation, controller connection…
cdf-video-data-augmentation
Run the CDF Video Data Augmentation Airflow workflow on Kubernetes or OSMO to create Cosmos video-to-video variants and auto-label both source and generated videos. Use for VDA payload authoring, preflight, execution, monitoring, output verification, or result retrieval. OSMO requires external endpoints. Standalone…
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.