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 OrcaQubits/agentic-commerce-skills-plugins --skill magento-deploygit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/magento-deploy)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-deploy"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-deploy/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/orcaqubits/agentic-commerce-skills-plugins/magento-deploy"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-deploy.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.00046 | $0.01204 |
| Opus 5 | $0.00023 | $0.00602 |
| Sonnet 5 | $0.00009 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
magento-deploy 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 3d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Deployment & CLI
Before writing code
Fetch live docs:
- Fetch
https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/set-modefor deployment modes - Fetch
https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/static-view/static-view-file-deploymentfor static content deploy - Web-search
magento 2 zero downtime deploymentfor zero-downtime strategies
Deployment Modes
| Mode | Errors | Static Files | DI Compilation | Use Case |
|---|---|---|---|---|
| Developer | Displayed | Generated on demand | Automatic | Local development |
| Production | Logged only | Pre-deployed | Pre-compiled | Live site |
| Default | Not displayed | On demand | Not optimized | Initial install |
bin/magento deploy:mode:show
bin/magento deploy:mode:set production
bin/magento deploy:mode:set developer
Production Deployment Steps
Standard Sequence
# 1. Enable maintenance mode
bin/magento maintenance:enable
# 2. Pull latest code (git pull, composer install)
composer install --no-dev --optimize-autoloader
# 3. Run setup upgrade (applies db_schema changes and patches)
bin/magento setup:upgrade
# 4. Compile DI (generates interceptors, factories, proxies)
bin/magento setup:di:compile
# 5. Deploy static content (CSS, JS, images, templates)
bin/magento setup:static-content:deploy en_US --jobs=4
# 6. Flush cache
bin/magento cache:flush
# 7. Disable maintenance mode
bin/magento maintenance:disable
Static Content Deploy Strategies
- quick — minimizes deployment time by reusing files across locales (default in 2.4+)
- compact — minimizes disk space
- standard — full deployment
- Flags:
--exclude-theme,--no-html-minify,--jobs=Nfor parallelism
Zero-Downtime Deployment
Pipeline Deployment
Build and deploy on separate systems:
- Build server:
setup:di:compile+setup:static-content:deploy - Transfer artifacts to production
- Production:
setup:upgrade --keep-generated(no recompilation)
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.
- 3d ago First seen · 150 lines · 46 tokens per session scan A f6cac1cade7f
magento-deploy is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,204 once invoked, about $0.0002 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-09-15.
Other skills, from other repositories
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
arwp-evidence-ci
Add ARWP verification, regression contracts, evidence receipts, scheduled audits, and CI to a website repository. Use when asked to continuously check ARWP quality, prevent agent/search regressions, monitor public interfaces, generate evidence, or prove that an ARWP implementation remains consistent over time. Keep…
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
archestra-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.