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 module-plugingit 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/module-plugin)<a href="https://agentmods.dev/skills/caravanglory/magehub/module-plugin"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/module-plugin/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/module-plugin"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/module-plugin.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.00024 | $0.01970 |
| Opus 5.5 | $0.00010 | $0.00788 |
| Sonnet 5.5 | $0.00005 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
module-plugin 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Development
Activation
Use When
- The task is to alter behavior of an existing public Magento method without modifying the original class.
- The task mentions before/after/around plugins, interceptors, plugin sortOrder, disabled plugins, or di.xml plugin configuration.
Do Not Use When
- The target method is final, static, non-public, constructor/destructor, or otherwise not interceptable.
- A service contract implementation, observer, preference, event, or layout/config extension point is the safer project convention.
Required Inputs
- Target class, public method signature, desired before/after/around behavior, area scope, and expected interaction with existing plugins.
- Whether the plugin must preserve side effects, exceptions, and return-value contract exactly.
Workflow
- Inspect the target method signature, return type, visibility, existing plugins, and area-specific di.xml before choosing a plugin type.
- Prefer before plugins for argument normalization and after plugins for return-value decoration; use around only when skipping or wrapping execution is required.
- Create the plugin class with strict types, exact parameter/return typing, and minimal dependencies.
- Register the plugin in the narrowest applicable di.xml scope with an intentional name and sortOrder.
- Verify compile and targeted behavior after adding or changing the plugin.
Guardrails
- Do not plugin final, static, private, protected, constructor, or destructor methods.
- Around plugins must call and return $proceed() unless the task explicitly requires blocking execution.
- Ask before pluginizing checkout, payment, customer authentication, inventory reservation, or price calculation flows. (approval required)
Verification
- Run bin/magento setup:di:compile or the project wrapper after adding plugin classes or di.xml entries.
- Run targeted unit/integration tests for the modified behavior and at least one pass-through case.
- When changing plugin sortOrder, inspect sibling plugins and report the final execution order.
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 · 275 lines · 24 tokens per session scan A 61ae84eb18c0
module-plugin is a skill published in the GitHub repository caravanglory/magehub (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,970 once invoked, about $0.0001 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
convex-billing
Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating).
cloudbase-wechat-integration
A guide for connecting CloudBase applications to WeChat services, including payments, official accounts, and user identity.
shopify-admin
Write or explain Admin GraphQL queries and mutations for apps and integrations that extend the Shopify admin. Use when the user wants to understand, design, or generate the operation itself—even before deciding how to run it. Do not choose admin first for app monetization—charging merchants for the app itself via app…
shopify-functions
Shopify Functions allow developers to customize the backend logic that powers parts of Shopify. Available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location…
gplay-purchase-verification
Server-side purchase verification for in-app products and subscriptions using Google Play Developer API. Use when implementing receipt validation in your backend.
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…