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 Eliyce/paqad-ai --skill regression-test-gengit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/regression-test-gen)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/regression-test-gen"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/regression-test-gen/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/eliyce/paqad-ai/regression-test-gen"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/regression-test-gen.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00480 |
| Opus 5.5 | $0.00005 | $0.00192 |
| Sonnet 5.5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
regression-test-gen 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.
What it actually says
What It Does
Generates regression recommendations that stay tightly scoped to changed behavior and are grouped by test layer so follow-up verification work is deliberate and efficient.
Use This When
Use this after a bug fix, refactor, or migration once the changed behavior is understood and you need to decide what regression coverage should prove it stays fixed.
Inputs
- Read the changed behavior, existing tests, and claimed verification scope first.
- Read the stack-specific testing guide that matches the project.
- Read
references/regression-layer-map.mdbefore proposing new coverage.
Procedure
- List the concrete behaviors changed by the request and ignore unrelated nearby surfaces.
- Map each changed behavior to the narrowest meaningful test layer that can catch regression.
- Reuse existing suites, fixtures, and patterns before suggesting new harnesses.
- Group recommendations by unit, integration, end-to-end, or manual verification layer.
- Call out any changed behavior that should remain manual only and explain why.
Output Contract
- Return sections named
Unit,Integration,End-to-End, andManual Verificationin that order. - Under each section, list only the changed behaviors that belong to that layer.
- If a layer has nothing to add, write
<Layer>: none.
Escalate / Stop Conditions
- Ask when the available test harness is unknown and would materially change the layer recommendation.
- Warn when a requested regression check is broader than the changed behavior and likely to create noise.
- Do not recommend generic full-suite reruns as a substitute for behavior-focused regression coverage.
Resources
references/regression-layer-map.mdruntime/capabilities/coding/stacks/laravel/references/tools/testing.mdagents/openai.yaml
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 · 65 lines · 13 tokens per session scan A 789a63835411
regression-test-gen is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 480 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.
Other skills, from other repositories
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
diagnosing-bugs
Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock the fix with a regression test.
knowledge-engineering-quality-and-delivery-unit-integration-and-shared-test-harnesses
A testing guide for the CLI and web interfaces, covering unit, integration, end-to-end, and real-process test setup with shared fixtures and cleanup.
test-writer
Generate comprehensive tests including unit, integration, and property-based tests.
auto-canary
A deployment health-check skill for testing whether a recently deployed or staging website is working. It runs build, end-to-end, and browser checks, then reports a pass, warning, or failure.
debugging
Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack…