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-eav-attributesgit 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-eav-attributes)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-eav-attributes"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-eav-attributes/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-eav-attributes"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-eav-attributes.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.00057 | $0.00930 |
| Opus 5 | $0.00028 | $0.00465 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
magento-eav-attributes 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 EAV & Attributes
Before writing code
Fetch live docs:
- Web-search
site:developer.adobe.com commerce php development components attributesfor attribute development guide - Web-search
site:developer.adobe.com commerce php tutorials backend custom-attributesfor attribute creation tutorial - Web-search
magento 2 EAV attribute data patchfor current patterns using data patches
Conceptual Architecture
What EAV Is
Entity-Attribute-Value is Magento's flexible storage pattern. Instead of one column per attribute, values are stored in separate typed tables. This allows merchants to add unlimited attributes without schema changes.
EAV Entities
Four entity types use EAV:
- Products (
catalog_product_entity) - Categories (
catalog_category_entity) - Customers (
customer_entity) - Customer Addresses (
customer_address_entity)
EAV Table Structure
Each entity has typed value tables:
*_entity— base entity table (entity_id, sku, type_id, etc.)*_entity_varchar— short text values*_entity_int— integer values (including boolean, select)*_entity_decimal— decimal/price values*_entity_datetime— date/time values*_entity_text— long text values
Attribute Properties
Key properties when creating attributes:
- type — backend storage type (varchar, int, decimal, datetime, text, static)
- input — frontend input type (text, textarea, select, multiselect, boolean, date, price, media_image, etc.)
- label — human-readable name
- required — is this attribute mandatory?
- source — source model for select/multiselect options
- backend — backend model for validation/processing
- frontend — frontend model for display formatting
- global — scope: store view, website, or global
- visible — shown in admin forms
- searchable — indexed for catalog search
- filterable — available as layered navigation filter
- comparable — shown in product comparison
- used_in_product_listing — available in category listing pages
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 · 91 lines · 57 tokens per session scan A 58f76ab5886a
magento-eav-attributes is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 930 once invoked, about $0.0003 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
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.…
archestra-dev-migrations
Use when changing Drizzle schemas, generating migrations, editing migration SQL, creating data-only migrations, diagnosing drizzle-kit check failures, or resolving migration/generated-client conflicts.
omni-db-backups
Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.
duckdb-analyst
Use for any analytical question over ./data/.parquet. Prefer DuckDB, always show the SQL.
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.