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/claim-issuenpx skills add loopdive/js2 --skill claim-issuegit 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.00064 | $0.00847 |
| Opus 5 | $0.00032 | $0.00424 |
| Sonnet 5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
claim-issue 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claim-issue — atomic cross-developer issue claim (#2168)
With several developers (humans + agents, possibly across forks) on the project, the in-memory TaskList is invisible to other devs. Before starting work on an issue you MUST take a git-backed lock so nobody else grabs the same task.
The lock lives on a dedicated orphan ref — refs/heads/issue-assignments on
origin — holding one <id>.json per claimed issue. Pushing there does not
move main, so it never rebuilds queued merge groups (#1951) and never triggers
CI. The first git push wins; a concurrent claimant gets a non-fast-forward
rejection, re-fetches, and re-evaluates.
Claim before you start
# Humans:
node scripts/claim-issue.mjs <id> <your-name>
# Dev agents — use your github-account-prefixed name:
node scripts/claim-issue.mjs <id> ttraenkler/<agent-name> --branch issue-<id>-<slug>
# (or set CLAIM_GITHUB_ACCOUNT=ttraenkler and pass just <agent-name>)
The script does the sync-and-check for you, in this order:
git fetch origin(the assignment ref andmain).- Refuse (exit 4) if the issue is already
done/wont-fixonorigin/main. - Refuse (exit 3) if it's already claimed by someone else — STOP and pick
another issue. (Pass
--forceonly to deliberately steal, e.g. reclaiming a suspended branch.) - Otherwise write
<id>.jsonand push to the ref immediately.
Interpret the exit code, don't just read the text:
0— you own it. Proceed: create your worktree, set the issue'sstatus: in-progress+assignee:in your branch (lazy reflection ontomainlands with your PR), implement.3— taken. Pick the next candidate.4— already closed on main. Skip; flag the tech lead to reconcile the queue.5— push kept getting rejected (heavy contention). Just re-run.
Inspect / release / complete
node scripts/claim-issue.mjs --list # all live claims (id, assignee, branch)
node scripts/claim-issue.mjs --check <id> # is #<id> free? (exit 0 free / 3 taken)
node scripts/claim-issue.mjs --release <id> <name> # abandon/suspend — frees it for others
node scripts/claim-issue.mjs --complete <id> # mark done when your PR merges
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 · 65 lines · 64 tokens per session scan A e72f4f44cbee
claim-issue is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 847 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.