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 agentmods add commands/khadinakbarlabs/shopify-app-builder/deploy-appgit clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote 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/khadinakbarlabs/shopify-app-builder/deploy-app)<a href="https://agentmods.dev/commands/khadinakbarlabs/shopify-app-builder/deploy-app"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/deploy-app.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00559 |
| Opus 5 | $0.00010 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
deploy-app 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy App to Production
You are releasing a Shopify app to production environment with proper versioning, health checks, and rollback capability.
Pre-Deployment Validation
-
Verify build and dependencies
- Run
npm run build(oryarn build) to compile Remix production build - Ensure no TypeScript compilation errors
- Verify all environment variables set for production (SHOPIFY_API_KEY, SHOPIFY_API_SECRET)
- Confirm database migrations applied to production schema
- Reference skill: CLI deployment (01_cli_scaffolding.md)
- Run
-
Security and compliance check
- Verify OAuth Token Exchange flow uses PKCE
- Confirm webhook signature verification enabled on all handlers
- Check API scopes follow principle of least privilege
- Ensure no hardcoded credentials in codebase
- Reference skill: authentication security (04_functions_auth_billing_mcp.md)
-
Test critical workflows
- Verify app installation flow completes without errors
- Test OAuth redirect and token exchange
- Confirm webhooks trigger and process events
- Validate billing API integration if applicable
- Reference skill: testing patterns (01_cli_scaffolding.md)
Deployment Execution
-
Release to production
- Execute
shopify app release --version [version-tag] - Confirm deployment pipeline (GitHub Actions or CI/CD system) succeeds
- Verify app assets uploaded to CDN
- Monitor deployment logs for errors
- Reference skill: CLI release workflow (01_cli_scaffolding.md)
- Execute
-
Verify production deployment
- Confirm app loads in production Shopify admin
- Test OAuth flow with production credentials
- Verify webhook tunnel points to production endpoint
- Check production logs for errors or warnings
- Monitor API rate limit usage from admin dashboard
-
Post-deployment configuration
- Enable production webhook topics if different from development
- Configure monitoring and alerting for error rates
- Set up logging aggregation (CloudWatch, Datadog, etc.)
- Create runbook for common production issues
- Reference skill: deployment configuration (01_cli_scaffolding.md)
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.
- 5d ago First seen · 67 lines · 21 tokens per session scan A 639a4fe2dfbc
deploy-app is a command published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 26d ago), licensed MIT. It adds 21 tokens to every session and 559 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.
Other commands, from other repositories
deploy-setup
Wire CI + secrets for a fresh storefront. Run once after /init-store before the first push to main.
boss:ship
只跑部署环节：DevOps 构建部署 + 上线前门禁 + 部署报告。对已通过测试的项目单独可用，产出 deploy-report.md，门禁不可绕过。.
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
wa-guardrails
Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) — so a workload stays aligned with Well-Architected best practices over time instead of being assessed once.
cost-optimization-review
Run a pillar-scoped Well-Architected review focused on the Cost Optimization pillar.
start-13-5.es
Bienvenido a Lección 13-5: Despliegue en Vercel.