medusa-subscribers

medusa-subscribers is a skill for Claude Code from OrcaQubits/agentic-commerce-skills-plugins. It costs 46 tokens per session (1,469 once invoked), scanned A, original, MIT.

A guide to Medusa v2 subscribers and scheduled jobs. Subscribers run code when events such as a product or order change occur, while scheduled jobs run on a timetable such as a cron schedule.

In plain words
What is it for?
Use it for notifications, follow-up processing, periodic maintenance, and other work triggered by Medusa events or schedules.
Why use it?
It helps you react to commerce events without blocking the operation that caused them. It also explains how to register handlers and choose an event system such as Redis or in-memory delivery.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the medusa-commerce plugin — 19 skills, 1 agent shipped together

Good fit Use it for notifications, follow-up processing, periodic maintenance, and other work triggered by Medusa events or schedules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers
Install

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.

Any agent
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill medusa-subscribers
Clone the repo
git clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-plugins

Made for: Claude Code.

Or install medusa-commerce, the plugin that ships this one along with the rest of its 19 skills, 1 agent.

Wrote 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.

agentmods badge for medusa-subscribers

README.md
[![agentmods](https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers/github.svg)](https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers)
Your own site
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers/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.

agentmods 80×15 button for medusa-subscribers

Your own site · 80×15
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-subscribers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01469
Opus 5 $0.00023 $0.00734
Sonnet 5 $0.00009 $0.00294
Haiku 4.5 $0.00005 $0.00147

Measured 2d ago against content hash 9a6d1122a527, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-16, from the pricing page.

Security

Grade A, and why

medusa-subscribers 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 2d 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.

medusa-commerce/skills/medusa-subscribers/SKILL.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Medusa v2 Subscribers and Scheduled Jobs

Before writing code

Fetch live docs:

  1. Fetch https://docs.medusajs.com/learn/fundamentals/events-and-subscribers for subscriber overview
  2. Web-search site:docs.medusajs.com subscriber handler function for handler API
  3. Web-search site:docs.medusajs.com scheduled jobs cron for scheduled job patterns
  4. Web-search site:docs.medusajs.com event module redis for event bus configuration
  5. Web-search site:docs.medusajs.com built-in events list for available event names

Subscriber Concept

Subscribers react to events emitted by Medusa workflows and services:

  • Asynchronous by default -- do not block the emitting operation
  • Registered as files in src/subscribers/
  • Each file exports a default handler function and a config object
  • Events follow a naming convention: {entity}.{action} (e.g., product.created)

Subscriber File Structure

src/subscribers/
├── product-created.ts     # Reacts to product.created
├── order-placed.ts        # Reacts to order.placed
└── customer-registered.ts # Reacts to customer.created

Each file is auto-discovered -- no manual registration required.

Subscriber Handler Pattern

// src/subscribers/product-created.ts
// Fetch live docs for SubscriberArgs and SubscriberConfig types
import type { SubscriberArgs, SubscriberConfig } from "@medusajs/framework"

export default async function productCreatedHandler(
  { event, container }: SubscriberArgs<{ id: string }>) {
  // event.data.id contains the entity ID — fetch live docs for payload shapes
}

Config Export

// Fetch live docs for SubscriberConfig options
export const config: SubscriberConfig = {
  event: "product.created",
}

Event Naming Conventions

Domain Event Examples
Products product.created, product.updated, product.deleted
Orders order.placed, order.canceled, order.completed
Customers customer.created, customer.updated
Cart cart.created, cart.updated
Fulfillment fulfillment.created, fulfillment.canceled
Payment payment.captured, payment.refunded
Inventory inventory-item.created
Auth invite.created, invite.accepted

Read the full file on GitHub · 196 lines

Changes

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.

  1. 2d ago First seen · 196 lines · 46 tokens per session scan A 9a6d1122a527

Subscribe to this mod's changes

medusa-subscribers is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,469 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.

Related

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-ai/archestra · 118 tokens

archestra-dev-llm-providers

Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.

archestra-ai/archestra · 49 tokens

archestra-dev-backend

Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.

archestra-ai/archestra · 40 tokens

archestra-dev-investigate

Use when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.

archestra-ai/archestra · 54 tokens

debridge

Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.

internet-court/internet-court-skill · 48 tokens

0g-compute

0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI…

internet-court/internet-court-skill · 85 tokens