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.svg" alt="Measured on agentmods" 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.00138 | $0.07704 |
| Opus 5 | $0.00069 | $0.03852 |
| Sonnet 5 | $0.00028 | $0.01541 |
| Haiku 4.5 | $0.00014 | $0.00770 |
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 3d 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 — 737 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
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).
Zig binary detection: Check build.zig for b.addExecutable(.{ .name = "..." }) calls or a src/main.zig file to confirm this is an executable project (not a library).
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.
- 3d 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 1mo ago), licensed MIT. It adds 138 tokens to every session and 7,704 once invoked, about $0.0007 per session on Opus 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-check
Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.
release
Evaluate readiness and publish to crates.io.
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
03-release-tag
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
release-patterns
PR creation, CI/CD validation, merge coordination, and release patterns. Use when creating pull requests, running pre-PR validation, checking CI status, coordinating merges, or managing releases. Do NOT use for routine development commits -- see safe-workflow skill instead.