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-securitygit 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-security)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-security/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-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-security.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.00891 |
| Opus 5 | $0.00023 | $0.00445 |
| Sonnet 5 | $0.00009 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
magento-security 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Security
Before writing code
Fetch live docs:
- Web-search
site:experienceleague.adobe.com commerce securityfor security best practices - Web-search
site:developer.adobe.com commerce php development securityfor developer security guide - Web-search
magento 2 security patches latestfor recent security updates
Content Security Policy (CSP)
What It Does
Protects against XSS and code injection by restricting which resources (scripts, styles, images, fonts) can load.
Configuration
etc/csp_whitelist.xml— whitelist external domains per CSP directive- Modes: report-only (logs violations) and restrict (blocks violations)
- Directives:
script-src,style-src,img-src,font-src,connect-src,frame-src
Adding Allowed Sources
Whitelist third-party domains for payment gateways, analytics, CDNs:
- Declare in
csp_whitelist.xmlunder the appropriate directive - Use
report-onlymode first to identify missing whitelists
Two-Factor Authentication (2FA)
- Mandatory for all admin users since Magento 2.4.0
- Supported providers: Google Authenticator, Duo Security, Authy, U2F keys
- Rate limiting on OTP validation (configurable retry limit and lockout)
- Cannot be disabled in production (security requirement)
CSRF Protection
form_key— 16-character token included in all admin forms- Validated on every POST request in admin
- SameSite cookie attribute prevents cross-site request forgery
- Admin Secret Key in URLs adds additional protection
Admin Security Configuration
Available at Stores > Settings > Configuration > Advanced > Admin > Security:
- Custom admin URL path (obscure the
/adminpath) - Add Secret Key to URLs
- Password lifetime (force periodic changes)
- Max login failures before lockout
- Lockout duration
- Session lifetime
- Allowed countries for admin access
Input Validation and Output Escaping
Input Validation
- Validate all user input on the server side
- Use Magento's validation classes and form validators
- Never trust client-side validation alone
- Validate types, lengths, formats, and allowed values
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 · 106 lines · 46 tokens per session scan A a50cc98fad93
magento-security 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 891 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
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.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…