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 caravanglory/magehub --skill hyva-module-compatibilitygit clone --depth 1 https://github.com/caravanglory/magehubWrote 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/caravanglory/magehub/hyva-module-compatibility)<a href="https://agentmods.dev/skills/caravanglory/magehub/hyva-module-compatibility"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/hyva-module-compatibility/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/caravanglory/magehub/hyva-module-compatibility"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/hyva-module-compatibility.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.00039 | $0.02615 |
| Opus 5.5 | $0.00016 | $0.01046 |
| Sonnet 5.5 | $0.00008 | $0.00523 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
hyva-module-compatibility 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 2mo 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyva Module Compatibility
Activation
Use When
- The task is to adapt a Luma-oriented Magento module, template, layout, or JavaScript behavior for Hyva.
- The task mentions Hyva, Alpine.js, Tailwind CSS, ViewModels, private content, or removing RequireJS/Knockout dependencies.
Do Not Use When
- The storefront is still Luma-only and the task explicitly targets Knockout, RequireJS, or LESS implementation.
- The task is an adminhtml UI component or backend-only module change.
Required Inputs
- Affected frontend route/template/layout handle, target Hyva theme or compatibility module, and existing Luma dependencies to replace.
- Whether the compatibility layer should live in the theme override or a dedicated module.
Workflow
- Inspect existing layout XML, PHTML, JS dependencies, customer-data usage, block methods, and theme/module ownership.
- Remove or replace Luma-only blocks and scripts with Hyva-compatible PHTML, Alpine.js, Tailwind classes, and ViewModels.
- Keep dynamic customer-specific data out of cacheable HTML; use private content events or Hyva helpers.
- Verify responsive storefront behavior and ensure Luma compatibility is not broken unless the task explicitly deprecates it.
Guardrails
- Do not ship RequireJS, Knockout, jQuery UI, or LESS-only assumptions in Hyva paths.
- Do not place sensitive or customer-specific data into full-page-cacheable markup.
- Ask before removing Luma compatibility from the base module. (approval required)
Verification
- Run the project frontend build or static-content command when templates, Tailwind config, or CSS assets change.
- Run targeted PHP tests for ViewModels or services when business logic moves out of blocks/templates.
- Browser-smoke the affected Hyva page at desktop and mobile widths when a local storefront is available.
Output Contract
- List the Luma dependencies removed, Hyva replacements added, cache/private-content handling, and storefront verification performed.
- State whether changes live in a theme override, compatibility module, or base module.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 310 lines · 39 tokens per session scan A e861408df6ab
hyva-module-compatibility is a skill published in the GitHub repository caravanglory/magehub (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 2,615 once invoked, about $0.0002 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 skills, from other repositories
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
external-purchases
US web checkout via the StoreKit External Purchase Link entitlement — currently 0% Apple commission (litigation ongoing), how to ship it safely, and how to architect for a commission flip so a future ruling is a config change, not a rewrite. Use when adding external purchase links, weighing web checkout vs IAP, or…
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
Product Photoshoot Workflow
A workflow for turning one product photo into a set of four e-commerce images from different visual directions.