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/dev-self-mergenpx skills add loopdive/js2 --skill dev-self-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.00054 | $0.06186 |
| Opus 5 | $0.00027 | $0.03093 |
| Sonnet 5 | $0.00011 | $0.01237 |
| Haiku 4.5 | $0.00005 | $0.00619 |
Grade A, and why
dev-self-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 yesterday.
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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev-self-merge <N>
Devs DO NOT enqueue. On a passing self-check, mark the task completed and stand down — the server-side
auto-enqueue.ymlworkflow enqueues (#2786). This skill's outcomes are MERGE (regression self-check passes → mark the task completed and stand down; you do NOT touch the merge queue) or ESCALATE (to tech lead). The PR is enqueued by the server-side workflow, not by you.Why devs no longer enqueue (#2786). The old model had the dev one-shot enqueue when green, with a background CI watcher to do it after stand-down. But that watcher is a child of the dev process — it died with the agent, so a green PR whose dev had stood down stranded un-enqueued (#2225, #2247). The fix moves enqueue to the one actor that is long-lived and outside agent lifecycle: the GitHub Actions workflow. Its
workflow_run-on-completion trigger fires right after the required-check workflows finish, and its grace window is now 0 (#2786), so it enqueues every just-green PR within ~one workflow-startup — no dependence on any agent surviving. The required checks arecheap gate (main-ancestor + lint),merge shard reports, andquality.The merge queue then re-validates on the merged state.
merge_groupre-runs the required checks (the regression-gate #1943 — the hard block), andauto-park(#2547) labels any PR that fails the merge_group re-runhold. The workflow's single trailing-add enqueue never loops, so it cannot cause the re-enqueue "cancellation churn" (memoryproject_merge_queue_requeue_cancels_run) that poll-loop re-adds caused on 2026-06-20.Backstops, not the mechanism: the workflow's ~30-min cron, and the tech lead's per-loop open-PR sweep (CLAUDE.md "Tech lead discipline") — both catch the rare stray the responsive
workflow_runrun misses (e.g. a PR the queue dropped on main-advance). Neither is the primary path.SECURITY — the workflow's author-trust gate is now load-bearing. With no dev enqueue, the workflow is the single enqueuer; it only enqueues PRs whose
authorAssociationis OWNER/MEMBER/COLLABORATOR. External contributor PRs are never auto-enqueued — they require a deliberate maintainer enqueue plus a greencla-check.
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.
- yesterday First seen · 433 lines · 54 tokens per session scan A 615dc4911f29
dev-self-merge is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 6,186 once invoked, about $0.0003 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.