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 agentmods add skills/reorder-js/reorder/local-devnpx skills add reorder-js/reorder --skill local-devgit clone --depth 1 https://github.com/reorder-js/reorderWrote 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/reorder-js/reorder/local-dev)<a href="https://agentmods.dev/skills/reorder-js/reorder/local-dev"><img src="https://agentmods.dev/badge/skills/reorder-js/reorder/local-dev.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00762 |
| Opus 5 | $0.00017 | $0.00381 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
local-dev scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
until curl -s -f http://localhost:9000/health >/dev/null 2>&1; do sleep 1; done How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local development in Medusa backend & Storefront
This skill describes how to sync local changes in the reorder plugin with an external Medusa backend and run both the Medusa backend and the subscription storefront as separate Antigravity background tasks.
Workflow Execution Steps for Agents
When requested to run /local-dev or start the local development environment:
Step 1: Initial Sync or Plugin Rebuild (Only when code changed)
If you modified the reorder plugin code and need to rebuild and push changes to yalc:
./.agents/scripts/sync-local-env.sh
[!NOTE] If the user simply requests to restart or start the backend/storefront without code changes, do NOT run
sync-local-env.sh. Skip directly to Step 2 and restart the process.
Step 2: Start Medusa Backend (Background Task)
Start the Medusa backend dev server using run_command with IsDaemon: true and working directory set to the backend directory (Cwd: /Users/tomaszkasperski/Desktop/Development/medusa-reorder/my-medusa-store):
yarn dev
Step 3: Wait for Backend Readiness
Poll http://localhost:9000/health until the backend responds with HTTP 200 OK before starting the storefront:
until curl -s -f http://localhost:9000/health >/dev/null 2>&1; do sleep 1; done
Step 4: Start Subscription Storefront (Background Task)
Start the storefront dev server as a separate background daemon task using run_command with IsDaemon: true and working directory set to the storefront directory (Cwd: /Users/tomaszkasperski/Desktop/Development/medusa-reorder/subscription-storefront):
yarn dev
Step 5: Report URLs to the User
Always immediately provide the clickable URLs:
- Medusa Backend API:
http://localhost:9000 - Medusa Admin Dashboard:
http://localhost:9000/app - Subscription Storefront:
http://localhost:8000
Manual Setup & Storefront Connection Requirements
1. Medusa Backend
- Install
yalcglobally if needed:npm i yalc -g - In the Medusa backend's
package.json, declare the plugin dependency using yalc:"@reorderjs/reorder": "file:.yalc/@reorderjs/reorder" - Ensure the plugin is registered in
medusa-config.ts. - Ensure PostgreSQL database is running and
DATABASE_URLis configured in.env. - Ensure CORS settings in backend
.envallow storefront access (STORE_CORS=http://localhost:8000,...).
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.
- 4d ago First seen · 69 lines · 35 tokens per session scan A ea31fd41e616
local-dev is a skill published in the GitHub repository reorder-js/reorder (52 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 762 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
saleor-paper-storefront
Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.
paper-migrations
Apply chronological Paper storefront upgrades to a forked shop. Use when the user says upgrade Paper, apply Paper migrations, catch up with upstream caching, or paper-version. Reads migrations/manifest.json and paper-version.json; ports architecture without overwriting custom styling.
storefront-best-practices
ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart…
learning-medusa
Load automatically when user asks to learn Medusa development (e.g., "teach me how to build with medusa", "guide me through medusa", "I want to learn medusa"). Interactive guided tutorial where Claude acts as a coding bootcamp instructor, teaching step-by-step with checkpoints and verification.
building-admin-dashboard-customizations
Load automatically when planning, researching, or implementing Medusa Admin dashboard UI (widgets, custom pages, forms, tables, data loading, navigation). REQUIRED for all admin UI work in ALL modes (planning, implementation, exploration). Contains design patterns, component usage, and data loading patterns that MCP…
building-with-medusa
Load automatically when planning, researching, or implementing ANY Medusa backend features (custom modules, API routes, workflows, data models, module links, business logic). REQUIRED for all Medusa backend work in ALL modes (planning, implementation, exploration). Contains architectural patterns, best practices, and…