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 agentmods add skills/buildinternet/releases-cli/releases-clinpx skills add buildinternet/releases-cli --skill releases-cligit clone --depth 1 https://github.com/buildinternet/releases-cliWhat 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 | $0.00086 | $0.02112 |
| Opus 5 | $0.00043 | $0.01056 |
| Sonnet 5 | $0.00017 | $0.00422 |
| Haiku 4.5 | $0.00009 | $0.00211 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 88 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 categories # valid --category values (fixed taxonomy)
Two commands built for agents specifically:
releases agent-context— emits a versioned JSON document describing every command, argument, and option. When in doubt about exact flags, call this instead of guessing; it's the CLI's machine-readable source of truth.releases skills install— installs/refreshes the bundled skills (-gfor user-wide). Symlinked by default, so re-running refreshes atomically.
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.
- 3d 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 3d ago), licensed MIT. It adds 86 tokens to every session and 2,112 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
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.sh", "here's our website, make us a manifest", declare a changelog /…
github
Prepare GitHub issues, pull requests, reviews, and release notes for Zhin projects. Use when asked to write an issue, PR description, changelog entry, or review comment. Triggers: 写 issue, PR 描述, 提 PR, release notes, gh pr.
managing-sources
How to create, delete, list, validate, and manage changelog sources — covers ignored/blocked URLs, duplicate detection, and the validation workflow.
maintaining-orgs
Routine maintenance of indexed organizations — fetch all sources, regenerate overviews, verify data quality. Use when asked to "update", "refresh", or "maintain" one or more orgs, or when doing periodic sweeps of the registry.
regenerating-overviews
Generate or refresh an org's AI overview from recent releases. Use when asked to "regenerate", "rewrite", or "refresh the overview" for one or more orgs, or as the regen step inside a maintaining-orgs run.
finding-changelogs
How to find, evaluate, and recommend the best ingestion method for changelog URLs — covers feed discovery, provider detection, GitHub API, markdown sources, and scraping fallback.