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 SocketDev/sauce --skill brew-publishgit clone --depth 1 https://github.com/SocketDev/sauceWrote 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/socketdev/sauce/brew-publish)<a href="https://agentmods.dev/skills/socketdev/sauce/brew-publish"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/brew-publish/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/socketdev/sauce/brew-publish"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/brew-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00061 | $0.00813 |
| Opus 5.5 | $0.00024 | $0.00325 |
| Sonnet 5.5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
brew-publish 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Homebrew tap (binary-download formula)
Model: no bottles, no source build - the formula downloads the release's
prebuilt per-platform tarballs by EXACT
releases/download/v<version>/<asset> URL (never latest) and pins the
sha256 the release's own checksums.txt vouched for. brew-publish NEVER
hashes an asset itself; the manifest is the authority.
Tap layout (one-time, manual)
The tap repo (SocketDev/homebrew-socket) carries an unsharded Formula/
dir plus a README documenting tap trust:
export HOMEBREW_REQUIRE_TAP_TRUST=1
brew trust SocketDev/socket
The exact layout is modeled by release-kit/examples/brew-cli/tap-fixture/
in sauce. Creating the tap repo is a human act (repo creation rights) -
note it plainly; there is no script.
Bump cycle
Prerequisite: the release is CUT - tag on origin, release published (not
draft), all four platform assets uploaded, checksums.txt attached (the
github-release flow produces all of this).
node scripts/socket-release/brew-publish.mts --tag vX.Y.Z # dry-run plan
node scripts/socket-release/brew-publish.mts --tag vX.Y.Z --apply # commit the bump
The tool refuses, in order, with exit 1 and zero writes: a tag not on
origin (it never creates tags), a draft/missing release, a missing
templated asset, a missing/incomplete checksums.txt. An identical formula
is a no-op (already reads <version>, exit 0). --apply commits the
formula DIRECT to the tap default branch with a GitHub-signed API commit
(never a PR - the version-bump-PR shape is guard-blocked), then re-reads
the tap: the committed bytes must parse back to the desired formula, or it
exits 1 saved-state-unproven.
From CI, brew-publish.yml runs on release: published (or manual
dispatch with tag + publish: true) and mints a per-run App token via
the ./.github/actions/socket-release-app-token composite from the
org-wide App credentials - org secrets are enterprise-wide; never treat
them as missing setup or a human task.
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 Changed a28155cc6e66
- 1mo ago First seen · 78 lines · 61 tokens per session scan A 812f5961eff0
brew-publish is a skill published in the GitHub repository SocketDev/sauce (3 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 813 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.