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 loopdive/js2 --skill analyze-regressiongit clone --depth 1 https://github.com/loopdive/js2Wrote 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/loopdive/js2/analyze-regression)<a href="https://agentmods.dev/skills/loopdive/js2/analyze-regression"><img src="https://agentmods.dev/badge/skills/loopdive/js2/analyze-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.
<a href="https://agentmods.dev/skills/loopdive/js2/analyze-regression"><img src="https://agentmods.dev/badge/skills/loopdive/js2/analyze-regression.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.00031 | $0.00614 |
| Opus 5.5 | $0.00012 | $0.00246 |
| Sonnet 5.5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
analyze-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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Regression
Diffs two test262 JSONL result files to find exactly which tests flipped status.
Steps
- List available result archives:
ls -lt /workspace/benchmarks/results/test262-results*.jsonl | head -10
- Pick the two files to compare (current vs previous):
CURRENT="/workspace/benchmarks/results/test262-results.jsonl"
PREVIOUS="/workspace/benchmarks/results/test262-results-YYYYMMDD-HHMMSS.jsonl"
- Build status maps and diff:
python3 -c "
import json
from collections import Counter
current, previous = {}, {}
with open('$CURRENT') as f:
for line in f:
r = json.loads(line)
current[r['file']] = r['status']
with open('$PREVIOUS') as f:
for line in f:
r = json.loads(line)
previous[r['file']] = r['status']
# Find flips
regressions = [] # was pass, now not
fixes = [] # was not pass, now pass
for test in set(current) | set(previous):
old = previous.get(test, 'missing')
new = current.get(test, 'missing')
if old == 'pass' and new != 'pass':
regressions.append((test, old, new))
elif old != 'pass' and new == 'pass':
fixes.append((test, old, new))
print(f'Regressions (pass→fail): {len(regressions)}')
for t, o, n in sorted(regressions)[:20]:
print(f' {n:15s} ← {o:15s} {t}')
if len(regressions) > 20:
print(f' ... and {len(regressions)-20} more')
print(f'\nFixes (fail→pass): {len(fixes)}')
for t, o, n in sorted(fixes)[:20]:
print(f' {n:15s} ← {o:15s} {t}')
if len(fixes) > 20:
print(f' ... and {len(fixes)-20} more')
# Categorize regressions by new status
regr_cats = Counter(n for _, _, n in regressions)
print(f'\nRegression breakdown: {dict(regr_cats)}')
"
- Report findings:
- Number of regressions and fixes
- Top regression patterns (which status did they flip to?)
- Common file paths (is it one codegen area?)
Output
Message with: "Regression analysis: +N fixes, -M regressions. Top pattern: [description]"
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 · 76 lines · 31 tokens per session scan A 17caa519e76e
analyze-regression is a skill published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 614 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.
Other skills, from other repositories
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.
insta-snapshots
Review and update Oxc Insta snapshots non-interactively after expected output changes or snapshot test failures.
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…
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…
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…
extending-personhog-test-harness
When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new…