Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/loopdive/js2npx agentmods add skills/loopdive/js2/claim-issueWrote 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/claim-issue)<a href="https://agentmods.dev/skills/loopdive/js2/claim-issue"><img src="https://agentmods.dev/badge/skills/loopdive/js2/claim-issue/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/claim-issue"><img src="https://agentmods.dev/badge/skills/loopdive/js2/claim-issue.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.00064 | $0.00847 |
| Opus 5.5 | $0.00026 | $0.00339 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 65 lines · 64 tokens per session scan A e72f4f44cbee
claim-issue is a skill published in the GitHub repository loopdive/js2 (66 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 847 once invoked, about $0.0003 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
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.