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/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 21 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.5 | $0.00010 | $0.00226 |
| Sonnet 5.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 2mo 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.
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.
- 2mo ago Changed · +2 lines · -12 tokens per session ca8bfc75b3ab
- 2mo 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 (59 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 564 once invoked, about $0.0001 per session on Opus 5.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.
run-tests compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| run-testsreorder-js/reorder | Skill | 59 | 12d ago | MIT | A | 24 | Claude Code, Codex |
| task-manageriamlukethedev/Claw3D | Skill | 2.4k | 2d ago | MIT | A | 56 | Claude Code, Codex |
| soundclawiamlukethedev/Claw3D | Skill | 2.4k | 2d ago | MIT | A | 18 | Claude Code, Codex |
| todoiamlukethedev/Claw3D | Skill | 2.4k | 2d ago | MIT | A | 12 | Claude Code, Codex |
| testingTeam-Commonly/commonly | Skill | 1.4k | yesterday | Apache-2.0 | A | 31 | Claude Code, Codex |
| test-harnessMathews-Tom/armory | Skill | 340 | 5d ago | MIT | A | 65 | Claude Code |
| authoring-data-quality-checksPostHog/posthog | Skill | 41k | yesterday | none | A | 174 | Claude Code, Codex |