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 jaktestowac/awesome-copilot-for-testers --skill analyzing-regression-scopegit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/analyzing-regression-scope)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/analyzing-regression-scope"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/analyzing-regression-scope/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/jaktestowac/awesome-copilot-for-testers/analyzing-regression-scope"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/analyzing-regression-scope.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.00065 | $0.01014 |
| Opus 5 | $0.00032 | $0.00507 |
| Sonnet 5 | $0.00013 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
analyzing-regression-scope 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzing Regression Scope
Use this skill when the real question is not "how do we test everything?" but "what must we retest now, and why?" It is built for risk-aware retest planning after code changes, configuration shifts, dependency updates, or release packaging.
When to Use
- analyze regression scope after a bug fix or feature change
- decide what must be retested for a hotfix
- prepare a release confidence suite from a diff or PR
- explain QA impact of shared component or config changes
- separate must-retest areas from nice-to-have regression coverage
Operating Principles
- Change surface first - understand what changed before proposing retest coverage.
- Risk spreads through dependencies - shared modules, auth, data mapping, and configuration often widen impact.
- Direct is not the whole story - the changed file is only the start; adjacent behaviors matter too.
- Small believable packs beat fake completeness - a focused confidence suite is better than a giant list nobody will execute.
- Unknown impact stays visible - if propagation is unclear, log it as an open question instead of bluffing.
Workflow
Phase 0: Frame the input
Use the best available source:
- changed files
- a diff or PR summary
- release notes
- a hotfix description
- a list of touched components or endpoints
Capture any known critical journeys, environments, or roles that matter.
Phase 1: Map the change surface
Break the change into four layers:
- Directly changed behavior - the feature, endpoint, or component that was edited
- Adjacent behavior - nearby flows that call, render, or depend on the changed surface
- Shared risk - utilities, configuration, auth, layout, data mapping, or common services reused elsewhere
- State and data risk - migrations, caching, permissions, synchronization, or environment-specific behavior
Phase 2: Classify retest risk
Use a practical three-level scale:
| Risk | Use when |
|---|---|
| High | Direct change on a critical path, shared core module, data integrity flow, auth, checkout, notifications, or high-traffic workflow |
| Medium | Indirect dependency, shared helper, UI shell, validation logic, or meaningful edge-case exposure |
| Low | Isolated change with narrow blast radius and no obvious shared-path impact |
What ships with it
1 file 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.
- 9d ago First seen · 117 lines · 65 tokens per session scan A 982fd58b5b54
analyzing-regression-scope is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 13d ago), licensed MIT. It adds 65 tokens to every session and 1,014 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
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…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…