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 agentmods add skills/loopdive/js2/merge-wavenpx skills add loopdive/js2 --skill merge-wavegit clone --depth 1 https://github.com/loopdive/js2What 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 | $0.00045 | $0.01566 |
| Opus 5 | $0.00023 | $0.00783 |
| Sonnet 5 | $0.00009 | $0.00313 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
merge-wave 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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Wave Protocol
Triage every open PR that has finished sharded test262 CI, compute its real net delta, and execute a ranked merge order in one pass.
When to use
- Multiple PRs ready to merge after a morning of dev work
- After a sprint's worth of issues finished CI at roughly the same time
- When you want to cross a pass-rate milestone in one batch
Step 1: Gather candidate PRs
gh pr list --limit 20 --json number,title,headRefName,mergeable,mergeStateStatus
Filter to PRs with mergeStateStatus: UNSTABLE | CLEAN | BEHIND — skip DIRTY (conflict, ping dev to refresh) and DRAFT.
Step 2: Download every PR's merged-report artifact
The sharded workflow uploads test262-merged-report per run. Find each PR's run ID via the merge shard reports check:
mkdir -p output/pr-artifacts
for pr in <LIST>; do
run_id=$(gh pr view $pr --json statusCheckRollup --jq '.statusCheckRollup[] | select(.name=="merge shard reports") | .detailsUrl' | grep -oE 'runs/[0-9]+' | head -1 | cut -d/ -f2)
mkdir -p output/pr-artifacts/pr-$pr
gh run download $run_id -n test262-merged-report -D output/pr-artifacts/pr-$pr >/dev/null 2>&1
done
Artifact filenames: test262-report-merged.json, test262-regressions.txt, test262-results-merged.jsonl.
Step 3: Compute and rank net deltas
BASELINE=$(python3 -c "import json; d=json.load(open('benchmarks/results/test262-current.json')); print(d['summary']['pass'])")
for pr in <LIST>; do
rpt=output/pr-artifacts/pr-$pr/test262-report-merged.json
[ -f "$rpt" ] && python3 -c "
import json
d=json.load(open('$rpt'))
s=d['summary']
delta=s['pass']-$BASELINE
print(f'PR #$pr pass={s[\"pass\"]} delta={delta:+d} ce={s[\"compile_error\"]}')
"
done | sort -t= -k3 -n -r
Step 4: Classify each PR
Thresholds (tune per context):
| Delta | Action |
|---|---|
| < −500 | CATASTROPHIC → close immediately with diagnosis. Do NOT merge. |
| −500 to −20 | Real regression → close, open follow-up issue, ask dev to investigate root cause |
| −20 to +20 | MARGINAL → check if regressions are false positives; if yes merge, if no close |
| +20 to +100 | GOOD → sample regressions, admin-merge if regressions are false positives or acceptable |
| +100+ | STRONG → admin-merge, flag regressions in a follow-up issue |
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.
- 2d ago First seen · 146 lines · 45 tokens per session scan A 6caa2043fe8a
merge-wave is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,566 once invoked, about $0.0002 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
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
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
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
babel-docs
Babel 7.x/8.x — plugins, presets, config, @babel/core, parser, traverse, types, CLI, preset-env.