handle-regression

handle-regression is a skill for Claude Code from loopdive/js2. It costs 32 tokens per session (2,004 once invoked), scanned A, original, Apache-2.0.

A procedure for investigating when the JavaScript test262 suite passes fewer tests than before. Test262 is a standard collection of tests used to check JavaScript implementations.

In plain words
What is it for?
Use it after a test262 run to compare pass and failure statuses, identify tests that stopped passing, group related failures, and guide the investigation and fix.
Why use it?
It helps distinguish a real regression—a change that breaks something previously working—from missing results or an ordinary first run. It compares current results with archived results and summarizes regressions and fixes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it after a test262 run to compare pass and failure statuses, identify tests that stopped passing, group related failures, and guide the investigation and fix.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/loopdive/js2/handle-regression
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 loopdive/js2 --skill handle-regression
Clone the repo
git clone --depth 1 https://github.com/loopdive/js2

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.

agentmods badge for handle-regression

README.md
[![agentmods](https://agentmods.dev/badge/skills/loopdive/js2/handle-regression/github.svg)](https://agentmods.dev/skills/loopdive/js2/handle-regression)
Your own site
<a href="https://agentmods.dev/skills/loopdive/js2/handle-regression"><img src="https://agentmods.dev/badge/skills/loopdive/js2/handle-regression/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.

agentmods 80×15 button for handle-regression

Your own site · 80×15
<a href="https://agentmods.dev/skills/loopdive/js2/handle-regression"><img src="https://agentmods.dev/badge/skills/loopdive/js2/handle-regression.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,004 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 83
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 101
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 115
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.02004
Opus 5.5 $0.00013 $0.00802
Sonnet 5.5 $0.00006 $0.00401
Haiku 4.5 $0.00003 $0.00200

Measured 1mo ago against content hash f06de6b5e22a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

handle-regression 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.

.claude/skills/handle-regression/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Handle Regression Protocol

Use this when a test262 run shows fewer passes than the baseline or previous run.

Step 1: Confirm the regression is real

# Compare current vs archived results
python3 -c "
import json, os
current = {}
with open('benchmarks/results/test262-results.jsonl') as f:
    for line in f:
        r = json.loads(line)
        current[r['file']] = r

archives = sorted([f for f in os.listdir('benchmarks/results')
                   if f.startswith('test262-results-') and f.endswith('.jsonl')])
if not archives:
    print('No archived results to compare. Run was the first.')
    exit()

prev = {}
with open(f'benchmarks/results/{archives[-1]}') as f:
    for line in f:
        r = json.loads(line)
        prev[r['file']] = r

regressions = [(t, prev[t]['status'], current[t]['status'], current[t].get('error','')[:60])
               for t in prev if prev[t]['status'] == 'pass' and current.get(t,{}).get('status') != 'pass']
fixes = [t for t in current if current[t]['status'] == 'pass' and prev.get(t,{}).get('status') != 'pass']

print(f'Regressions: {len(regressions)}, Fixes: {len(fixes)}, Net: {len(fixes) - len(regressions):+d}')

from collections import Counter
patterns = Counter()
for t, old, new, err in regressions:
    if 'SyntaxError' in err: patterns['expected SyntaxError but compiled'] += 1
    elif 'null' in err.lower(): patterns['null deref'] += 1
    elif new == 'compile_error': patterns['new compile error'] += 1
    elif 'returned' in err: patterns['wrong return value'] += 1
    else: patterns[err[:30] or new] += 1

print()
print('Regression patterns:')
for p, c in patterns.most_common(10):
    print(f'  {c:4d}  {p}')

print()
print('Sample regressions (1 per pattern):')
shown = set()
for t, old, new, err in sorted(regressions):
    for p in patterns:
        if p not in shown and p[:15] in (err + new)[:60]:
            print(f'  {t}')
            shown.add(p)
            break
    if len(shown) >= 5: break
"

If regressions < 10 and could be flaky tests, re-run test262 to confirm.

Read the full file on GitHub · 223 lines

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.

  1. 1mo ago First seen · 223 lines · 32 tokens per session scan A f06de6b5e22a

Subscribe to this mod's changes

handle-regression is a skill published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 2,004 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-08-30.

Related

Other skills, from other repositories

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog · 112 tokens

playwright-e2e-testing

Production-grade Playwright end-to-end testing skill for AI coding agents. Provides specialized guidance for writing, debugging, and maintaining Playwright tests in TypeScript, JavaScript, and Python. Covers the full testing lifecycle: test structure and architecture (Page Object Model, fixtures, custom matchers)…

JPeetz/agent-skills · 316 tokens

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

insta-snapshots

Review and update Oxc Insta snapshots non-interactively after expected output changes or snapshot test failures.

oxc-project/oxc · 25 tokens

fixing-flaky-tests

Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when hogli ci:insights or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a…

PostHog/posthog · 220 tokens

extending-hobby-smoke-tests

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data…

PostHog/posthog · 83 tokens