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 sampleXbro/agentsmesh --skill homebrew-packaginggit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/homebrew-packaging)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/homebrew-packaging"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/homebrew-packaging/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/samplexbro/agentsmesh/homebrew-packaging"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/homebrew-packaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00438 |
| Opus 5.5 | $0.00015 | $0.00175 |
| Sonnet 5.5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
homebrew-packaging 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.
What it actually says
Purpose
Homebrew Packaging
You are responsible for Homebrew distribution of a CLI or executable package that may be implemented in TypeScript/Node.
Goals
- Ensure Homebrew installation is reproducible.
- Keep formula updates correct and easy to review.
- Align GitHub release assets with Homebrew expectations.
- Avoid brew distribution when the package is not a real CLI product.
Applicability
Use this skill only when the project distributes an actual command-line tool or executable artifact. If the project is only an importable npm library, do not recommend Homebrew as a primary distribution channel.
Packaging principles
- Homebrew is for installable tools.
- Release assets must be stable and versioned clearly.
- Checksums must match the exact published archive.
- Installation instructions must be tested on a clean macOS environment where possible.
Checklist
Verify:
- the package exposes a real CLI entry point
- GitHub release assets are versioned consistently
- archive naming is predictable
- SHA256 is computed from the final release artifact
- formula URLs match the release layout
- install step places binaries correctly
brew installandbrew testpaths are valid
Formula guidance
When generating or updating a formula:
- use stable release URLs
- update version and checksum together
- keep dependencies explicit
- include a meaningful
test doblock - avoid brittle install logic when possible
Node/TS-specific concerns
For Node-based CLIs, check whether you are distributing:
- raw source requiring Node at install/runtime
- bundled JS output
- standalone binary via a packager
Document runtime requirements clearly.
Output format
When assisting with brew packaging, provide:
- Whether Homebrew is appropriate
- Required release asset format
- Formula changes
- Validation steps
- User-facing install instructions
Do not overcomplicate the formula. Optimize for stable installs.
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 First seen · 68 lines · 37 tokens per session scan A eb0e1a2075c5
homebrew-packaging is a skill published in the GitHub repository sampleXbro/agentsmesh (26 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 438 once invoked, about $0.0001 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-30.
Other skills, from other repositories
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
release-notes
Drafts concise release notes from merged pull requests and conventional commits. Use when the user asks for a changelog, release notes, or a GitHub release body.
fork-and-publish-skill
Customizes an installed agent skill and ships it back upstream or as a versioned fork using qvr's edit/publish authoring loop. Use when a user wants to modify, customize, fork, release, or publish a qvr skill — e.g. "edit this skill", "publish my changes", "fork a skill to my own repo", "cut a v1.0.0 release of a…
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
deploy-check
Confirm build outputs, environment variables, release notes, and rollback steps before touching deployment configuration.