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-check)<a href="https://agentmods.dev/commands/commerce-atoms/agents/deploy-check"><img src="https://agentmods.dev/badge/commands/commerce-atoms/agents/deploy-check/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-check"><img src="https://agentmods.dev/badge/commands/commerce-atoms/agents/deploy-check.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.00026 | $0.00736 |
| Opus 5.5 | $0.00010 | $0.00294 |
| Sonnet 5.5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
deploy-check 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-check
Doctrine reminder (
AGENTS.md §0sub-doctrine): the agent prepares and validates. CI deploys. This command validates locally;ci.ymlruns the same gates on PR +push:main, and Shopify'soxygen-deployment-<storefrontId>.ymldeploys once the code lands onmain.
Reproduce the CI validation gates locally before git push. If anything fails, fix it and re-run. Do not push a broken change and rely on CI to catch it. The Shopify-provisioned deployer has no pre-deploy validation of its own (it just runs shopify hydrogen deploy); the safety net is ci.yml + branch protection.
Prerequisites
- Working tree should ideally be clean. Uncommitted changes are validated but flagged.
- Dependencies installed (
npm installornpm ci).
Workflow
Run each step in order. Stop on the first failure and surface the output to the operator.
1. Working tree status
git status --porcelain
If output is non-empty, surface a warning: "Uncommitted changes detected. They will be excluded from the push but included in the local pre-flight."
2. Codegen
npm run codegen
Must succeed. If GraphQL fragments / types drift, codegen reports it; commit any regenerated files before proceeding.
3. TypeScript
npm run typecheck
Zero errors required.
4. Lint
npm run lint
Zero errors required. Warnings are surfaced but do not block.
5. Tests
npm test
Full unit + integration suite. All green.
6. Build
npm run build
Production build must succeed. Bundle-size regressions are not blocking but are surfaced.
7. Architecture validation
npx @commerce-atoms/agents validate-architecture
Zero errors required (the validate-architecture skill).
8. Summary
If all eight steps pass, print:
PRE-FLIGHT PASSED — safe to push.
Push when ready:
git push origin main
Or, if the change warrants a release: /release
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 31276c19a2d3
- 1mo ago First seen · 111 lines · 26 tokens per session scan A f4c97c2bb120
deploy-check is a command published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 736 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
workflow-automate
Automate CI/CD pipelines, releases, and development workflows with GitHub Actions, pre-commit hooks, and infrastructure automation.
arrange-workspace-flow-technical-context
Phase 4 Technical context of arrange-workspace-flow.
fastapi_stripe
A Stripe Checkout implementation takes four steps.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
ink-art
Hand-drawn ink-on-white doodle animation — a character that draws itself then walks/dances/waves, or a deadpan contraption explainer. Vector, deterministic, rendered via HyperFrames to MP4.