Release instructions for publishing a public Bex Security package version across its source repository, npm, Git tags, and GitHub releases. npm is a package registry for JavaScript software.

Preparing, validating, publishing, tagging, and announcing an explicitly requested Bex Security release.

They enforce matching versions, a clean main branch, safe Git history, and protected handling of registry credentials.

How bex-co/bex-security configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bex-co/bex-security. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bex-co/bex-security/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bex-co/bex-security

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bex-co/bex-security/release/github.svg)](https://agentmods.dev/skills/bex-co/bex-security/release)

Your own site

<a href="https://agentmods.dev/skills/bex-co/bex-security/release"><img src="https://agentmods.dev/badge/skills/bex-co/bex-security/release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bex-co/bex-security/release"><img src="https://agentmods.dev/badge/skills/bex-co/bex-security/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,005 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.01005
Opus 5.5	$0.00017	$0.00402
Sonnet 5.5	$0.00009	$0.00201
Haiku 4.5	$0.00004	$0.00101

Measured 1mo ago against content hash 5ea61cbbdfca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release 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.

.claude/skills/release/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Bex Security

Publish one immutable @bex-co/bex-security version from main. A successful release has the same version in sdk/typescript/package.json, npm, the bex-v<version> Git tag, and the GitHub release.

Preconditions

Read the repository AGENTS.md instructions and review all material that will become public.
Require a clean worktree on main. Never stash, discard, amend, rebase a published commit, or force-push.
Fetch origin and the canonical openai/codex-security upstream. Bring local main to origin/main with a fast-forward only.
Confirm sdk/typescript/package.json names @bex-co/bex-security, points to the Bex repository, and retains codex-security only as a compatibility bin.
Authenticate to the public npm registry. When .env provides NPM_TOKEN, load it without printing it and pass it only through the process environment:
```
env "npm_config_//registry.npmjs.org/:_authToken=$NPM_TOKEN" npm whoami --registry=https://registry.npmjs.org
```
Do not create or commit an npm credentials file.

Choose The Version

Resolve the merged upstream baseline with git merge-base main upstream/main. Read the upstream package version from that commit rather than claiming an unmerged upstream release.

Versions are <upstream-version>-bex.<release-number>.
Use .1 for the first Bex release on a new upstream version.
Otherwise increment the greatest published Bex release number for that exact upstream version.
Never reuse, overwrite, deprecate, or unpublish a version.
If npm already contains the intended version, enter recovery mode: do not bump or publish it again; verify the archive and complete only missing Git or GitHub release metadata.

Update these fields together:

version
bex.upstreamVersion
bex.upstreamCommit
.github/bex-release-notes.md release marker, heading, summary, highlights, and upstream base

Release notes must describe user-visible Bex behavior generically. Do not copy private scan targets, findings, credentials, customer context, local paths, or unreviewed commit messages into public metadata.

Read the full file on GitHub · 98 lines

Changes

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 · 98 lines · 43 tokens per session scan A 5ea61cbbdfca

Subscribe to this mod's changes

release is a skill published in the GitHub repository bex-co/bex-security (53 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,005 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.

Claude Code Git and workflow Releases acp agent-client-protocol ai-security application-security code-scanning

update-v8-version

Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.

openinterpreter/openinterpreter · 86 tokens

bex-security: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release Bex Security

Preconditions

Choose The Version

What this file has done since we first saw it

Other skills, from other repositories

update-v8-version

managing-archestra-releases

archestra-merge-queue

github-release-notes-generator

archive-helper

release-notes-summary