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 cboone/agent-harness-plugins --skill set-up-installersgit 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/skills/cboone/agent-harness-plugins/set-up-installers)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/set-up-installers"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/set-up-installers/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/cboone/agent-harness-plugins/set-up-installers"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/set-up-installers.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.00059 | $0.07791 |
| Opus 5.5 | $0.00024 | $0.03116 |
| Sonnet 5.5 | $0.00012 | $0.01558 |
| Haiku 4.5 | $0.00006 | $0.00779 |
Grade B, and why
set-up-installers scanned grade B 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get update How it starts
The opening of the file, as written. The whole thing — 740 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set-Up Installers
Set up installer and distribution methods for a project. Supports Go, Swift, Rust, and Zig projects.
Installer types:
- Homebrew: a Homebrew tap formula for
brew install - go install: compatibility and README instructions for
go install(Go only) - cargo install: compatibility and README instructions for
cargo install(Rust only)
Workflow
To add or configure GoReleaser publishing for an existing Go CLI, run ./references/goreleaser/workflow.md. To write, update or review a formula in an existing tap, run only ./references/homebrew-formula/workflow.md. Preserve existing project files in both modes; neither requires the full installer setup below.
1. Detect Project Type
Scan the project to determine its language and structure:
| Marker | Language | Notes |
|---|---|---|
go.mod |
Go | Also check for .goreleaser.yml/.goreleaser.yaml |
Package.swift |
Swift | Check for macOS-only constraints |
Cargo.toml |
Rust | Check for binary targets |
build.zig |
Zig | Check for executable targets |
Additional checks regardless of language:
- Check for a
Makefile - Run
gh repo view --json owner,name,descriptionto get GitHub repo info
Go sub-detection: If .goreleaser.yml or .goreleaser.yaml exists, note that GoReleaser is already configured (this affects Homebrew and release workflow steps).
Swift platform detection: Check for macOS-only constraints:
- Grep source files for AppKit, Cocoa, or macOS-specific framework imports
- Look for conditional compilation or macOS-only availability checks (for example
#if os(macOS),canImport(AppKit)) - If inconclusive, ask the user whether the project is macOS-only or cross-platform
Rust binary detection: Check Cargo.toml for [[bin]] sections, a src/main.rs file, or binaries under src/bin/ (for example, src/bin/*.rs) to confirm this is a binary crate (not a library).
What ships with it
12 files beside SKILL.md 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.
- references/goreleaser/conditional-features.md 7.5 KB
- references/goreleaser/goreleaser-base.md 3.7 KB
- references/goreleaser/homebrew-tap-token.md 2.8 KB
- references/goreleaser/makefile-targets.md 1.2 KB
- references/goreleaser/migration-guide.md 1.8 KB
- references/goreleaser/release-workflow.md 1.9 KB
- references/goreleaser/workflow.md 8.1 KB
- references/homebrew-formula/cboone-tap.md 3.9 KB
- references/homebrew-formula/homebrew-current.md 4.0 KB
- references/homebrew-formula/patterns.md 4.2 KB
- references/homebrew-formula/validation.md 1.9 KB
- references/homebrew-formula/workflow.md 5.4 KB
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.
- 8d ago Changed · +4 lines · +3 tokens per session 611af74666dd
- 13d ago Changed · +1 lines · +21 tokens per session 9d85939420e4
- 29d ago Changed 5bbd4dde6a52
- 1mo ago Changed 919f90b9827e
- 1mo ago Changed · -7 lines · -103 tokens per session ae11c08df9db
- 1mo ago Changed · +5 lines 83a850077b4b
- 1mo ago First seen · 737 lines · 138 tokens per session scan B 684db05faab0
set-up-installers is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 7,791 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
starcat-cli-release
A release process for Starcat’s command-line program and its Homebrew package. Homebrew is a tool for installing software on macOS and Linux from package definitions.
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.
release
Build, sign, notarize, and publish a new DroidProxy release. Use when the user wants to cut a release, merge a PR and ship it, or asks to build/notarize/publish. Covers the full pipeline: PR merge, version bump, swift build, code signing, Apple notarization, Sparkle appcast update, and GitHub release creation.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
pr
Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it.