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/wipe-test-datanpx skills add reorder-js/reorder --skill wipe-test-datagit 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/wipe-test-data)<a href="https://agentmods.dev/skills/reorder-js/reorder/wipe-test-data"><img src="https://agentmods.dev/badge/skills/reorder-js/reorder/wipe-test-data.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.1 | $0.00033 | $0.00246 |
| Opus 5 | $0.00016 | $0.00123 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
wipe-test-data 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 6d 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.
What it actually says
Reset Test Data (Transactional Wipe)
Wipes all transactional data (order, cart, customer, subscription, plan_offer, renewal_cycle, dunning_case, cancellation_case, subscription_log, subscription_metrics_daily) using TRUNCATE CASCADE. Products, catalog, and admin users are preserved.
⚠️ Mandatory Confirmation
NEVER execute this script immediately.
- Warn the user that this will permanently delete 100% of operational data (orders, customers, subscriptions, renewals, dunning, analytics, logs).
- Ask for explicit confirmation.
- Execute only after the user explicitly confirms (e.g., "yes", "tak", "proceed").
Execution (Only After Confirmation)
Run from the Medusa backend directory:
cd ../my-medusa-store && npx medusa exec ../reorder/scripts/wipe-test-data.ts
After execution, inform the user that the transactional data has been wiped.
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.
- 6d ago First seen · 26 lines · 33 tokens per session scan A 8526e48d83b6
wipe-test-data is a skill published in the GitHub repository reorder-js/reorder (53 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 246 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-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…
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…
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-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…