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.
curl -O https://raw.githubusercontent.com/reorder-js/reorder/main/.agents/skills/run-tests/SKILL.mdgit 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/run-tests)<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>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.00564 |
| Opus 5 | $0.00012 | $0.00282 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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.
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
- Run focused tests for the affected area only.
- Self-contained fixtures: Never depend on manual DB state or prior test runs. Seed in
beforeEachwith unique IDs (Date.now()). - 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).
- Admin API (
- Mutation Pattern:
- Set up
page.waitForResponse(...)before triggering UI mutation. - Trigger action (click button, submit modal, confirm prompt).
- Assert HTTP status (200) + request payload (
postDataJSON()) or response body (json()).
- Set up
- 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).
- Toast visibility (
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.
- yesterday Changed · +2 lines · -12 tokens per session ca8bfc75b3ab
- 7d ago First seen · 43 lines · 36 tokens per session scan A 3093797a8d56
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.
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".
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…
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.
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.
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.
Write Tests
Generate unit and integration tests.