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/test-and-mergenpx skills add loopdive/js2 --skill test-and-mergegit 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.00043 | $0.00501 |
| Opus 5 | $0.00022 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
test-and-merge 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 3d 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.
What it actually says
Test and Merge Pipeline
Devs run this themselves after implementing a fix. There is no separate tester agent — CI handles test262, and devs self-merge when CI passes.
Step 1: Merge main into branch
cd /workspace/.claude/worktrees/<branch>
git fetch origin && git merge origin/main
- Clean merge: proceed
- Conflicts in
dashboard/,plan/,public/:git checkout --theirs <file>, thenpnpm run build:planning-artifacts - Conflicts in
src/**/*.ts: create[CONFLICT]task in TaskList for senior-developer. STOP.
Step 2: Run equivalence tests
npm test -- tests/equivalence.test.ts
All equivalence tests must pass. Any new failure = regression, fix before pushing.
Step 3: Push and open PR
git push origin <branch>
gh pr create --base main --title "fix(#N): <description>" --body "..."
Step 4: Wait for CI
Use a foreground blocking loop — keeps the agent occupied until CI result lands:
until [ -f /workspace/.claude/ci-status/pr-<N>.json ] && \
[ "$(jq -r '.head_sha' /workspace/.claude/ci-status/pr-<N>.json)" = "$(git rev-parse HEAD)" ]; \
do sleep 60; done
Step 5: Self-merge via /dev-self-merge
Run /dev-self-merge <N> — outputs MERGE or ESCALATE.
- MERGE:
gh pr merge <N> --merge --admin - ESCALATE: message tech lead with criterion, values, PR number
Step 6: Post-merge cleanup
git worktree remove /workspace/.claude/worktrees/<branch>TaskUpdate(status: completed)TaskList→ claim next task, or shut down if queue is empty
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.
- 3d ago First seen · 58 lines · 43 tokens per session scan A 369c776a2d76
test-and-merge is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 501 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.