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.
git 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/plugins/socketdev/sauce/socket-release)<a href="https://agentmods.dev/plugins/socketdev/sauce/socket-release"><img src="https://agentmods.dev/badge/plugins/socketdev/sauce/socket-release.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
socket-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 yesterday.
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
{
"name": "socket-release",
"source": "./skills/socket-release",
"skills": "./",
"description": "Stand up SocketDev publishing (npm, crates.io, GitHub releases, Homebrew tap) in a repo: copy in the release kit and run its bootstrap - name reservation, GitHub environments, npm trusted publisher, staged publish config, verification."
}What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 325 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#socket-release in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 6 lines scan A 7d33d8edfc95
socket-release is a plugin published in the GitHub repository SocketDev/sauce (2 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-05.
Other plugins, from other repositories
ship
Complete PR workflow from commit to production with validation.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
org-management
GitHub organisation management including CI health, dependency audits, issue triage, maintenance, orchestration, releases, standards, and repo monitoring.
charon
Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.
beecount-release
A release workflow for BeeCount projects that coordinates version tags, change logs, website updates and video copy across two code repositories. A release is the process of publishing a new software version.