What is testing.reorder?

A Python test-organization workflow that puts test classes and functions in the same order as the code they check. Python is a programming language commonly used for scripts and applications.

Use it to reorder tests for a Python file without changing their logic or behavior.

It makes a test file easier to compare with its source file while preserving how the tests work.

testing.reorder — Skill for Claude Code by causify-ai/helpers

Install

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.

Any agent

npx skills add causify-ai/helpers --skill testing.reorder

Clone the repo

git clone --depth 1 https://github.com/causify-ai/helpers

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/causify-ai/helpers/testing.reorder/github.svg)](https://agentmods.dev/skills/causify-ai/helpers/testing.reorder)

Your own site

<a href="https://agentmods.dev/skills/causify-ai/helpers/testing.reorder"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/testing.reorder/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/causify-ai/helpers/testing.reorder"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/testing.reorder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 483 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, 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 Excessive Agency · line 3
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00483
Opus 5.5	$0.00006	$0.00193
Sonnet 5.5	$0.00003	$0.00097
Haiku 4.5	$0.00002	$0.00048

Measured 1mo ago against content hash c77bbec31e15, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing.reorder 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 1mo 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.

.claude/skills/testing.reorder/SKILL.md · 71 lines

What it actually says

Goal

Reorganize the Python test classes and functions in a testing file */test/test_*.py to match the order of the functions they test in the corresponding source file

Conventions

For all the code you must follow the instructions in
- .claude/skills/coding.rules.md
- .claude/skills/testing.rules.md

Workflow

Find Test Code

Find the functions in <FILENAME>.py that are tested in the file test/test_<FILENAME>.py

Prepare a Plan

Prepare a plan that shows a mapping between
- Test classes
- The functions tested by each class
- The file containing the tested functions

Order the Testing Classes in the Same Order as the Python File

Reorganize the code in test/test_<FILENAME>.py to match the order of the functions declared in <FILENAME>.py

E.g., if in a Python .../file.py

def test1(...)

def test2(...)

the corresponding .../test/test_file.py

class Test_test1(...)

class Test_test2(...)

Preserve Behavior Exactly

Do not modify functionality, logic, signatures, control flow, side effects, or semantics
The resulting code must behave identically to the original

Move Code Only

The refactor must be structural only
Allowed changes:
- Reordering functions
- Adding section headers
- Renaming internal/private functions consistently
Disallowed changes:
- Rewriting logic
- Simplifying implementations
- Changing APIs
- Changing imports unnecessarily
- Modifying formatting beyond what is required for reorganization

Implement the Plan

Implement the plan moving the code without changing it
Run the related unit tests to make sure everything works

Verification

Confirm test classes appear in the same order as the functions they test
Run the related unit tests and confirm they pass
Confirm no logic, signatures, or behavior changed

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.

1mo ago Changed · +5 lines · -2 tokens per session c77bbec31e15
1mo ago First seen · 66 lines · 17 tokens per session scan A 982e63a94864

Subscribe to this mod's changes

testing.reorder is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 483 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-09-03.

Testing Unit testing

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

testing.reorder