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/commerce-atoms/agentsWrote 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/commerce-atoms/agents/deploy-setup)<a href="https://agentmods.dev/commands/commerce-atoms/agents/deploy-setup"><img src="https://agentmods.dev/badge/commands/commerce-atoms/agents/deploy-setup/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/commerce-atoms/agents/deploy-setup"><img src="https://agentmods.dev/badge/commands/commerce-atoms/agents/deploy-setup.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.00033 | $0.01554 |
| Opus 5.5 | $0.00013 | $0.00622 |
| Sonnet 5.5 | $0.00007 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
deploy-setup 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-setup
Doctrine reminder (
AGENTS.md §0sub-doctrine): the agent prepares and validates. CI deploys. This command wires CI; it never runsshopify hydrogen deploy.
Wire deploy CI for a fresh storefront. The pipeline has two independent workflows with distinct jobs:
- Validation gate.
.github/workflows/ci.yml, runs on every PR +push:main. Blocks merge via branch protection. - Deployer.
.github/workflows/oxygen-deployment-<storefrontId>.yml, auto-provisioned by Shopify when a Hydrogen storefront is created in Shopify Admin. Runs on every push (any branch): production onmain, preview URL on every other branch.
Because Shopify owns the deployer (auto-managed deployment token, one file per Hydrogen storefront), the operator's job is to accept it. Not to author it.
Prerequisites
- Repo bootstrapped via
/init-store. ghCLI authenticated against the repo's GitHub org.- Shopify Partner account with a Hydrogen storefront created (Oxygen-hosted). Creating the Hydrogen storefront in Shopify Admin is what triggers the auto-provisioned PR.
Workflow
1. Verify the validation gate is present
test -f .github/workflows/ci.yml || echo "FAIL: missing .github/workflows/ci.yml"
Confirm ci.yml includes a Validate architecture step invoking npx --yes @commerce-atoms/agents validate-architecture. If missing, surface. This is what preserves the boundary check now that Shopify owns the deployer.
2. Wait for (or find) Shopify's auto-provisioned deploy PR
When a Hydrogen storefront is created (or linked) in Shopify Admin, Shopify's GitHub App opens a PR titled Set up Oxygen deployment workflow file on the connected repo, adding .github/workflows/oxygen-deployment-<storefrontId>.yml and setting the OXYGEN_DEPLOYMENT_TOKEN_<storefrontId> secret.
Find it:
gh pr list --search "Set up Oxygen deployment workflow file" --state open --json number,title,author,headRefName
If nothing is returned:
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 Changed · +36 lines · +7 tokens per session d06d9f3262cc
- 1mo ago First seen · 97 lines · 26 tokens per session scan A 94901a78b32b
deploy-setup is a command published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,554 once invoked, about $0.0001 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 commands, from other repositories
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
workflow-automate
Automate CI/CD pipelines, releases, and development workflows with GitHub Actions, pre-commit hooks, and infrastructure automation.
data-pipeline
Design and implement batch and streaming data pipelines with ingestion, orchestration, dbt transformations, data quality checks, and monitoring.
arrange-workspace-flow-technical-context
Phase 4 Technical context of arrange-workspace-flow.
fastapi_stripe
A Stripe Checkout implementation takes four steps.
new-pipeline
Scaffold a CI/CD pipeline for Azure infrastructure deployment — GitHub Actions or Azure DevOps.