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 skills add loopdive/js2 --skill test-and-mergegit clone --depth 1 https://github.com/loopdive/js2Wrote 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/test-and-merge)<a href="https://agentmods.dev/skills/loopdive/js2/test-and-merge"><img src="https://agentmods.dev/badge/skills/loopdive/js2/test-and-merge/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/test-and-merge"><img src="https://agentmods.dev/badge/skills/loopdive/js2/test-and-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 55 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00043 | $0.00501 |
| Opus 5.5 | $0.00017 | $0.00200 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (67 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 501 once invoked, about $0.0002 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
insta-snapshots
Review and update Oxc Insta snapshots non-interactively after expected output changes or snapshot test failures.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
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…