reorder: Skill for Claude Code

.agents/skills/run-tests/SKILL.md

run-tests is a skill for Claude Code, Codex from reorder-js/reorder. It costs 24 tokens per session (564 once invoked), scanned A, original, MIT.

A testing guide for the Reorder plugin, covering unit tests and integration tests, which check that separate parts of the software work together.

In plain words
What is it for?
Use it to run HTTP integration tests, module integration tests, or the full test suite, and to update tests for changed routes, workflows, scheduling, or state transitions.
Why use it?
It helps developers choose focused tests, prepare independent test data, and keep tests aligned with changes to the plugin.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is reorder-js/reorder's own configuration. It tells Claude Code and Codex how to work on reorder itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything reorder configures →

Reuse

Borrowing it

Nothing to install: this file belongs to reorder-js/reorder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/reorder-js/reorder/main/.agents/skills/run-tests/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/reorder-js/reorder

Made for: Claude Code, Codex.

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 run-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/reorder-js/reorder/run-tests.svg)](https://agentmods.dev/skills/reorder-js/reorder/run-tests)
Your own site
<a href="https://agentmods.dev/skills/reorder-js/reorder/run-tests"><img src="https://agentmods.dev/badge/skills/reorder-js/reorder/run-tests.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 564 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.00024 $0.00564
Opus 5 $0.00012 $0.00282
Sonnet 5 $0.00005 $0.00113
Haiku 4.5 $0.00002 $0.00056

Measured yesterday against content hash ca8bfc75b3ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

run-tests 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 yesterday.

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.

.agents/skills/run-tests/SKILL.md · 45 lines

How it starts

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

Testing in Reorder

Commands

# Backend integration tests (Jest)
yarn test:integration:http                        # All HTTP integration tests
yarn test:integration:modules                     # All module integration tests
TEST_TYPE=integration:http NODE_OPTIONS=--experimental-vm-modules jest --runInBand integration-tests/http/<file>.spec.ts

# Browser E2E tests (Playwright — requires running Medusa backend on :9000)
yarn test:e2e                                     # Full suite (seed -> auth -> chromium)
npx playwright test e2e/<file>.spec.ts            # Single spec
npx playwright test e2e/<file>.spec.ts --project=chromium  # Run spec reusing existing auth
npx playwright test e2e/<file>.spec.ts --headed   # Visual / headed mode
npx playwright test e2e/<file>.spec.ts --debug    # Step-by-step debugger

Core Rules

  1. Run focused tests for the affected area only.
  2. Self-contained fixtures: Never depend on manual DB state or prior test runs. Seed in beforeEach with unique IDs (Date.now()).
  3. Doc sync: If plugin behavior changes, keep docs/ and tests aligned.

Playwright E2E Conventions (e2e/)

  • Page Object Model: Place reusable page classes in e2e/pages/ (encapsulate locators, navigation, actions, and assertions).
  • Data Seeding:
    • Admin API (request.newContext()): Seed catalog entities (products, variants) via Medusa API (POST /admin/products).
    • Direct SQL (execFileSync("psql", [DB_URL, "-c", sql])): Seed domain entities lacking Admin creation endpoints (subscription, renewal_cycle).
  • Mutation Pattern:
    1. Set up page.waitForResponse(...) before triggering UI mutation.
    2. Trigger action (click button, submit modal, confirm prompt).
    3. Assert HTTP status (200) + request payload (postDataJSON()) or response body (json()).
  • UI Assertions:
    • Toast visibility (expect(page.getByText(...)).toBeVisible()).
    • StatusBadge text transitions (Active -> Paused).
    • Modal / Drawer closes (expect(modal).toBeHidden()).
    • State-dependent menu items (assert presence of valid actions and absence of invalid ones).

Read the full file on GitHub · 45 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. yesterday Changed · +2 lines · -12 tokens per session ca8bfc75b3ab
  2. 7d ago First seen · 43 lines · 36 tokens per session scan A 3093797a8d56

Subscribe to this mod's changes

run-tests is a skill published in the GitHub repository reorder-js/reorder (53 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 564 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

test-harness

Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".

Mathews-Tom/armory · 65 tokens

authoring-data-quality-checks

Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplicates, add data…

PostHog/posthog · 161 tokens

JavaScript Testing Patterns

Modern JavaScript testing strategies with Jest, Mocha, and testing best practices covering unit testing, integration testing, mocking, async patterns, and DOM testing.

PramodDutta/qaskills · 36 tokens

Jasmine Testing

BDD-style JavaScript testing with Jasmine covering spies, async patterns, custom matchers, clock manipulation, and comprehensive test organization for frontend and Node.js applications.

PramodDutta/qaskills · 35 tokens

jest-expert

Expert in Jest unit testing framework, mocks, snapshots, coverage reports, watch mode, and custom matchers. Use when the user mentions testing, unit testing, JavaScript, QA, mocking, or snapshots, or when the task involves Jest Framework, Test Structure, Advanced Features, or Basic Unit Tests.

personamanagmentlayer/pcl · 65 tokens

Write Tests

Generate unit and integration tests.

OpenLabor/openlabor · 8 tokens