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 regression-consistency-checkergit 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/regression-consistency-checker)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/regression-consistency-checker"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/regression-consistency-checker/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/regression-consistency-checker"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/regression-consistency-checker.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.00130 | $0.01908 |
| Opus 5.5 | $0.00052 | $0.00763 |
| Sonnet 5.5 | $0.00026 | $0.00382 |
| Haiku 4.5 | $0.00013 | $0.00191 |
Grade A, and why
regression-consistency-checker 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 2mo 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Consistency Checker
Check whether a new version of a repository preserves the behavior observed by tests on the old version.
Workflow
1. Prepare Versions
Set up old version:
# Tag or note the old version
git tag old-version
# Or checkout specific commit
git checkout <old-commit-hash>
Set up new version:
# Tag the new version
git tag new-version
# Or checkout new commit
git checkout <new-commit-hash>
Ensure clean environment:
- Same dependencies installed
- Same test configuration
- Same environment variables
- Deterministic test execution (fix random seeds, mock time)
2. Run Tests on Old Version
Capture baseline results:
# Python (pytest with JSON report)
git checkout old-version
pytest --json-report --json-report-file=old_results.json
# JavaScript (Jest with JSON report)
git checkout old-version
npm test -- --json --outputFile=old_results.json
# Run multiple times to check stability
pytest --json-report --json-report-file=old_results_1.json
pytest --json-report --json-report-file=old_results_2.json
# Compare to ensure deterministic
Verify baseline stability:
- All tests should pass (or document known failures)
- Results should be consistent across runs
- No flaky tests
3. Run Tests on New Version
Capture new results:
# Python
git checkout new-version
pytest --json-report --json-report-file=new_results.json
# JavaScript
git checkout new-version
npm test -- --json --outputFile=new_results.json
Note any immediate failures:
- Tests that now fail
- New errors or exceptions
- Changed behavior
4. Compare Results
Use comparison script:
python scripts/compare_results.py old_results.json new_results.json
# With custom tolerance for floats
python scripts/compare_results.py old_results.json new_results.json --tolerance 0.001
# Save detailed report
python scripts/compare_results.py old_results.json new_results.json --output regression_report.json
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.
- 2mo ago First seen · 348 lines · 130 tokens per session scan A ea28e9c904ed
regression-consistency-checker is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (260 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 130 tokens to every session and 1,908 once invoked, about $0.0005 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
skill-playwright
Browser automation and end-to-end testing with Playwright. Use when building/testing frontends, automating user workflows, taking screenshots, validating UI state, filling forms, testing across browsers, or mentions "playwright", "E2E test", "browser automation", "screenshot".
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
dev-ship
Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…
skill-code-quality
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
skill-pr-review
Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.