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.
npx skills add ArabelaTso/Skills-4-SE --skill java-regression-test-generatorgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/java-regression-test-generator)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/java-regression-test-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/java-regression-test-generator/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/arabelatso/skills-4-se/java-regression-test-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/java-regression-test-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00111 | $0.03499 |
| Opus 5.5 | $0.00044 | $0.01400 |
| Sonnet 5.5 | $0.00022 | $0.00700 |
| Haiku 4.5 | $0.00011 | $0.00350 |
Grade A, and why
java-regression-test-generator 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.
How it starts
The opening of the file, as written. The whole thing — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Regression Test Generator
Automatically generate regression tests for Java code based on version changes.
Overview
This skill analyzes changes between old and new versions of Java code and generates regression tests that ensure previously tested behavior still works while covering new or modified functionality. It preserves correctness guarantees from existing tests and suggests updates when old tests become invalid.
How to Use
Provide:
- Old version: The previous version of Java code
- New version: The updated version of Java code
- Existing tests: Test classes or methods for the old version
- Framework (optional): JUnit 5 (default) or TestNG
The skill will:
- Analyze changes between versions
- Identify modified, added, or removed functionality
- Generate regression tests for the new code
- Suggest updates for invalid existing tests
- Produce executable test code ready for integration
Test Generation Workflow
Step 1: Analyze Code Changes
Compare old and new versions to identify changes:
Method-level changes:
- Signature changes (parameters, return type)
- Logic modifications (algorithm, error handling)
- New methods added
- Methods removed
Class-level changes:
- Field additions or removals
- Constructor changes
- Inheritance modifications
- Access modifier changes
Dependency changes:
- New dependencies injected
- Dependency injection patterns added
- External API changes
Step 2: Classify Change Types
Categorize each change to determine test generation strategy:
Type 1: Signature Changes
- Parameter added/removed/reordered
- Return type changed
- Exception declarations modified
Type 2: Behavioral Changes
- Algorithm optimized (same behavior)
- Error handling added
- Validation logic added
Type 3: Structural Changes
- New methods/classes added
- Methods/classes removed
- Refactoring (extract method, rename)
Type 4: Dependency Changes
- Constructor injection added
- Dependencies replaced
- Mock requirements changed
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 554 lines · 111 tokens per session scan A 76e02d117374
java-regression-test-generator is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (257 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 3,499 once invoked, about $0.0004 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.
Other skills, from other repositories
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…
131-java-testing-unit-testing
Use when you need to review, improve, or write Java unit tests — including migrating from JUnit 4 to JUnit 5, adopting AssertJ for fluent assertions, structuring tests with Given-When-Then, ensuring test independence, applying parameterized tests, mocking dependencies with Mockito, verifying boundary conditions…
421-frameworks-quarkus-testing-unit-tests
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource /…
java-unit-test-generator
Generates JUnit unit tests for Java classes with loop prevention and incremental generation. Triggers on: "generate unit tests", "create JUnit tests", "test Java class", "add test coverage".
java-affected-tests
Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer runs the Java integration tests (they run only in the merge queue) and the JavaUIIT/search-it suites run only nightly, so this selects the unit tests and…