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.
/plugin marketplace add cboone/agent-harness-pluginsnpx agentmods add plugins/cboone/agent-harness-plugins/add-goreleaser-homebrewgit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/cboone/agent-harness-plugins/add-goreleaser-homebrew)<a href="https://agentmods.dev/plugins/cboone/agent-harness-plugins/add-goreleaser-homebrew"><img src="https://agentmods.dev/badge/plugins/cboone/agent-harness-plugins/add-goreleaser-homebrew.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
add-goreleaser-homebrew 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 5d 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
{
"author": {
"name": "Christopher Boone"
},
"description": "Add GoReleaser and Homebrew tap publishing to an existing Go CLI project with conditional support for completions, man pages, and macOS-only builds.",
"homepage": "https://github.com/cboone/agent-harness-plugins",
"keywords": ["github-actions", "go", "golang", "goreleaser", "homebrew"],
"license": "MIT",
"name": "add-goreleaser-homebrew",
"repository": "https://github.com/cboone/agent-harness-plugins",
"skills": "./skills",
"version": "2.3.3"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 149 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago First seen · 14 lines scan A 17c8ac313cda
add-goreleaser-homebrew is a plugin published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed 1mo ago), 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-08-31.
Other plugins, from other repositories
go-release
Release engineering for Go modules and applications — semantic versioning, breaking-change detection, deprecation conventions, go.mod hygiene, and binary distribution with GoReleaser.
google-go-style
Skill that codifies the Google Go Style Guide into actionable rules for writing, reviewing, and refactoring Go code.
jwx-dev-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse and sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid common footguns.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
golang-dev
Comprehensive Go development experience - skills that elevate Claude into the ultimate Golang developer.
claude-go
Go language support: goimports auto-formatting on file edits, Go coding conventions.