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/publish-releasenpx skills add loopdive/js2 --skill publish-releasegit 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.00183 | $0.02456 |
| Opus 5 | $0.00092 | $0.01228 |
| Sonnet 5 | $0.00037 | $0.00491 |
| Haiku 4.5 | $0.00018 | $0.00246 |
Grade A, and why
publish-release scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
not the egress proxy — `curl -sS "$HTTPS_PROXY/__agentproxy/status"` showing How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/publish-release — cut a release and push the version tag
Two npm packages ship in lockstep, plus JSR:
| package | manifest |
|---|---|
@loopdive/js2 |
root package.json |
js2wasm (proxy that re-exports the scoped package) |
packages/js2wasm/package.json |
.github/workflows/publish-npm.yml fires on any v* tag push and publishes
all three. The authoritative reference is
docs/releasing.md; this skill is the operator
protocol on top of it.
The one thing that makes this dangerous
Pushing the tag IS the publish. There is no confirmation step and no
practical undo — npm unpublish is heavily restricted, and JSR versions are
immutable. Everything below exists so the tag goes up exactly once, pointing at
reviewed code that is already on main.
So the ordering is not stylistic:
Push the branch. Get it merged. Only then push the tag.
A tag pushed before merge publishes un-reviewed code to the public registry.
Never hand-write a version tag (#389)
git tag vX.Y.Z on its own is the bug this flow was built to kill. The publish
workflow ships whatever version field package.json carries at the tagged
commit — not the tag name. Releases used to be bare tags that never touched
the manifest, so the published version sat pinned at 0.52.0 across thousands
of commits while the tags kept climbing. An external tester found it.
Two consequences worth holding onto:
- Version tags come exclusively from
scripts/release.mjs. If you catch yourself typinggit tag v…, stop — you are re-introducing #389. - Sprint-end tags
sprint/N, nevervX.Y.Z. The two are unrelated.
Step 1 — bump, commit, tag (one command, clean tree)
node scripts/release.mjs 0.70.0 # explicit version
node scripts/release.mjs patch # or a semver keyword: patch | minor | major
The script resolves one concrete version and applies the same string to four
places: the root manifest, the proxy manifest, the proxy's
dependencies["@loopdive/js2"], and jsr.json (which carries its own version
field and is what JSR publishes). Then it makes one commit
release: vX.Y.Z and one annotated tag vX.Y.Z on your branch. It also drafts
docs/release-notes/vX.Y.Z.md from the commit subjects since the last release
tag, amends it into the commit, and re-points the tag.
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.
- 2d ago First seen · 212 lines · 183 tokens per session scan A a4b983ad6c3c
publish-release is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed 2d ago), licensed Apache-2.0. It adds 183 tokens to every session and 2,456 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chrome-release-verify
End-to-end Chrome security backport for an Electron release branch. Given a Chrome Releases blog URL and a branch (e.g. 41-x-y), determines which CVE fixes are missing from the actual synced source, writes the cherry-pick patches locally, validates them with e sync --3 + lint --patches, then pushes a single PR. Use…
update-changelog
Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
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.
changeset
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit .changeset/.md release-note text. Do not use for implementation details or PR descriptions.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.