What is testing.move_test_code?

A procedure for dividing a large unit-test file into separate files based on the functions its test classes check. Unit tests are small automated checks of individual pieces of code.

Use it to map test classes to the code they cover, propose a split for approval, move the tests, and run them afterward.

It reduces clutter and makes it easier to find tests for a particular function without changing the test logic.

testing.move_test_code — Skill for Claude Code by gpsaggese/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 gpsaggese/helpers --skill testing.move_test_code

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/testing.move_test_code/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/testing.move_test_code)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/testing.move_test_code"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/testing.move_test_code/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/gpsaggese/helpers/testing.move_test_code"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/testing.move_test_code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 251 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.

Model	Per session	Once invoked
Fable 5.1	$0.00012	$0.00251
Opus 5.5	$0.00005	$0.00100
Sonnet 5.5	$0.00002	$0.00050
Haiku 4.5	$0.00001	$0.00025

Measured yesterday against content hash 7b4cefff04b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing.move_test_code 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.

.claude/skills/testing.move_test_code/SKILL.md · 38 lines

What it actually says

Goal

The user passes a file with unit tests <TEST_FILE>

Workflow

Find Tested Functions

Find the functions that are tested in the file <TEST_FILE>
Prepare a plan that shows a mapping between
- Test classes
- The functions tested by each class
- The file containing the tested functions

Propose Split Plan

Propose a plan to split the test classes in multiple files to match the code they test
- E.g., Test_func1, testing the function func1 in funcs.py should go in test_funcs.py

Get User Confirmation

Ask the user to confirm the plan

Implement the Plan

Implement the plan moving the code without changing it

Important

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

Verification

Run the moved tests and confirm they still pass
Confirm no test logic changed during the move

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.

yesterday First seen · 38 lines · 12 tokens per session scan A 7b4cefff04b8

Subscribe to this mod's changes

testing.move_test_code is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 251 once invoked, about $0.0000 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-11-06.

Testing Unit testing

testing.move_test_code next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
testing.move_test_codegpsaggese/helpers	Skill	158	today	Apache-2.0	A	12	Claude Code
test-masterJeffallan/claude-skills	Skill	12k	8d ago	MIT	A	104	Claude Code
migrate-xunit-to-xunit-v3dotnet/skills	Skill	5.8k	today	MIT	A	149	Claude Code
go-testingGentleman-Programming/gentle-ai	Skill	8.5k	today	MIT	A	26	Claude Code, Codex
principle-test-behavior-not-implementationmichael-denyer/pstack-claude	Skill	4.1k	yesterday	MIT	A	50	Claude Code
dart-testdartsim/dart	Skill	1.2k	today	BSD-2-Clause	A	18	Claude Code, Codex
test-generatorrshankras/claude-code-apple-skills	Skill	867	today	MIT	A	33	Claude Code