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 buildinternet/releases-cli --skill releases-cligit clone --depth 1 https://github.com/buildinternet/releases-cliWrote 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/buildinternet/releases-cli/releases-cli)<a href="https://agentmods.dev/skills/buildinternet/releases-cli/releases-cli"><img src="https://agentmods.dev/badge/skills/buildinternet/releases-cli/releases-cli/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/buildinternet/releases-cli/releases-cli"><img src="https://agentmods.dev/badge/skills/buildinternet/releases-cli/releases-cli.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.00098 | $0.02325 |
| Opus 5.5 | $0.00039 | $0.00930 |
| Sonnet 5.5 | $0.00020 | $0.00465 |
| Haiku 4.5 | $0.00010 | $0.00232 |
Grade A, and why
releases-cli 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 16d 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.
This is a copy
95% identical to releases-cli — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
releases CLI
The releases CLI is a first-class, keyless way to query the public changelog registry at releases.sh — the terminal peer of the Releases MCP. Anyone can search, tail, list, and inspect releases with no account and no API key; it talks to api.releases.sh by default with zero configuration. (A separate, invite-only admin surface exists for maintainers — see the short note at the end — but reads never need it.)
Reach for the CLI when the user is working in a shell or wants piped/scriptable output; reach for the MCP when you're answering conversationally with typed tools. They cover the same registry.
Install
brew install buildinternet/tap/releases # recommended on macOS / Linux
npm install -g @buildinternet/releases # or via npm
npx @buildinternet/releases search "react" # one-off, no install
Reader commands (no auth, no key)
Full reference: references/reader.md. The shape is verb-first, and every command takes --json.
releases search "breaking change" # unified search: orgs, catalog, collections, releases
releases tail next-js # latest releases from one source (slug or src_…)
releases tail --org vercel --count 20 # latest across a whole org
releases list --category ai # browse sources (alias: `releases sources`)
releases list --query shadcn # name / slug / url substring
releases get vercel # inspect any entity by id or slug
releases lookup domain vercel.com # resolve a domain/URL to its registry entry
releases collection list # browse curated cross-org playlists
releases collection releases frontier-ai-labs # the feed for one collection
releases stats # registry overview
releases changelog # recent product updates from releases.sh
releases categories # valid --category values (fixed taxonomy)
Two commands built for agents specifically:
What ships with it
2 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.
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.
- 16d ago Changed · +12 tokens per session 93937607858e
- 27d ago Changed · +4 lines daeb92da63f7
- 1mo ago Changed · +2 lines 86ba04f33356
- 1mo ago Changed · +1 lines 45691e8cb146
- 1mo ago First seen · 88 lines · 86 tokens per session scan A 80676cdbd18b
releases-cli is a skill published in the GitHub repository buildinternet/releases-cli (4 stars, last pushed 11d ago), licensed MIT. It adds 98 tokens to every session and 2,325 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to releases-cli, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
generating-release-content
Generate the AI fields on releases — titlegenerated, titleshort, summary, and composition — for one release, a window, or a backfill, via Claude Code sub-agents and direct SDK calls (OpenRouter/DeepSeek to match production summarize). Use when iterating on prompts, running provider/model experiments, or filling in a…
parsing-changelogs
How the Releases fetch and parse pipeline works — covers feed vs scrape adapters, incremental vs bulk parsing, dry-run testing, crawl mode, content hashing, and enrichment.
grouping-releases
Group releases that cover the same underlying launch so readers see one story instead of three. Use when manually curating an org's coverage — reconciling a window of recent releases, fixing a bad automatic grouping, or linking coverage the deterministic clusterer can't see. Decide which item is the best entry point…
creating-releases-json
Create or update a releases.json manifest so registries and agents can find where a company or project publishes its release notes. Use this whenever someone wants to "list our product on Releases", "add a releases.json", "get indexed on Releases Index", "here's our website, make us a manifest", declare a changelog /…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.