agentmods.dev

deploy-setup

A setup command for connecting a Shopify Hydrogen storefront to GitHub Actions, Shopify Oxygen’s hosting service, and the required secrets.

In plain words
What is it for?
Use it after initializing a storefront to verify the deployment workflow and configure GitHub secrets, environment variables, and Oxygen tokens.
Why use it?
It removes the manual setup needed before pushes to the main branch can trigger a deployment. The agent prepares and checks the connection, while CI performs the deployment.

Command

1 4mo ago A scan 26 tokens original MIT
View the source file commerce-atoms/agents
Install

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.

agentmods
npx agentmods add commands/commerce-atoms/agents/deploy-setup
Clone the repo
git clone --depth 1 https://github.com/commerce-atoms/agents
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,003 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.01003
Opus 5 $0.00013 $0.00502
Sonnet 5 $0.00005 $0.00201
Haiku 4.5 $0.00003 $0.00100

Measured yesterday against content hash 94901a78b32b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

kit/commands/deploy-setup.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/deploy-setup

Doctrine reminder (AGENTS.md §0 sub-doctrine): the agent prepares and validates. CI deploys. This command wires CI; it never runs shopify hydrogen deploy.

Wire GitHub Actions secrets, environment variables, and Oxygen tokens so that git push origin main deploys the storefront via CI — and not via the agent.

Prerequisites

  • Repo bootstrapped via /init-store (or otherwise mirroring the canonical layout).
  • gh CLI authenticated against the repo's GitHub org.
  • Shopify Partner account with Hydrogen storefront created (Oxygen-hosted).

Workflow

  1. Verify the deploy workflow is present.

    test -f .github/workflows/deploy.yml || echo "FAIL: missing .github/workflows/deploy.yml"

    If missing, copy .github/workflows/deploy.yml from hydrogen-storefront-starter.

  2. Inventory required secrets. Based on the canonical workflow:

    Secret Where to get it
    OXYGEN_DEPLOYMENT_TOKEN Shopify Admin → Hydrogen → Storefront → Settings → Deployment tokens
    SHOPIFY_STOREFRONT_API_TOKEN Shopify Admin → Apps → Hydrogen → API credentials
    SHOPIFY_STOREFRONT_ID Hydrogen storefront ID (URL slug in Shopify Admin)
    PUBLIC_STOREFRONT_API_VERSION Pinned Storefront API version (e.g. 2026-04)

  3. Set them. For each secret above, prompt the operator for the value and run:

    gh secret set OXYGEN_DEPLOYMENT_TOKEN --body "<value>"
gh secret set SHOPIFY_STOREFRONT_API_TOKEN --body "<value>"
gh secret set SHOPIFY_STOREFRONT_ID --body "<value>"
gh secret set PUBLIC_STOREFRONT_API_VERSION --body "<value>"

    Do not echo the values back to chat. Do not commit any of them to the repo.

  4. Document local equivalents. Verify .env.example lists the same keys. Update if missing. Confirm .env is gitignored.

  5. Smoke-check the workflow file.

Read the full file on GitHub · 97 lines

Changes

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.

  1. yesterday First seen · 97 lines · 26 tokens per session scan A 94901a78b32b

Subscribe to this mod's changes

deploy-setup is a command published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,003 once invoked, about $0.0001 per session on Opus 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.

Data and AIDevOps and cloudE-commerceaiai-agentscopilotcursorcursor-rules
Related

Other commands, from other repositories

fastapi_stripe

A Stripe Checkout implementation takes four steps.

iloveitaly/llm-ide-rules · 0 tokens

core-review

Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).

sanmak/specops · 0 tokens

resolve-conflicts

Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.

sanmak/specops · 0 tokens

ship-pr

Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.

sanmak/specops · 0 tokens

brownfield-map

Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.

wednesday-solutions/ai-agent-skills · 0 tokens

react-router-client-loader

Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.

iloveitaly/llm-ide-rules · 0 tokens