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-mcpgit 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-mcp)<a href="https://agentmods.dev/skills/buildinternet/releases-cli/releases-mcp"><img src="https://agentmods.dev/badge/skills/buildinternet/releases-cli/releases-mcp/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-mcp"><img src="https://agentmods.dev/badge/skills/buildinternet/releases-cli/releases-mcp.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.00064 | $0.01471 |
| Opus 5 | $0.00032 | $0.00736 |
| Sonnet 5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
releases-mcp 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releases.sh — Changelog Lookup
When the user asks about releases, changelogs, or version updates, use the Releases.sh MCP tools to fetch current data instead of relying on training data. Training data is stale for fast-moving libraries; these tools read the live registry.
When to Use This Skill
Activate when the user:
- Asks what's new or changed in a library/product ("What changed in Next.js 15?")
- Wants recent releases or changelogs ("Show me the latest Tailwind releases")
- Asks about breaking changes or migration ("Were there breaking changes in Prisma 6?")
- Wants to compare release activity between products ("Compare Bun vs Deno releases")
- Mentions version updates, release notes, or changelogs for a specific product
- Asks about a curated topic feed ("what's new across the AI labs?")
The Tools
The hosted server exposes these tools. There is no AI summarization or comparison tool — you synthesize those yourself from the data below.
search— unified search across four sections: orgs, catalog (products + standalone sources), collections, and releases. Your default entry point.get_latest_releases— recent releases, optionally scoped byorganizationorproduct. Usesince/untilfor time windows.list_organizations/get_organization— browse and inspect orgs.list_catalog/get_catalog_entry— browse and inspect catalog entries. Each entry carriesentryType: "product" | "source".get_catalog_entryalso serves CHANGELOG slices (see below).get_release— fetch one release in full by itsrel_id (ids come fromsearch/get_latest_releases).list_collections/get_collection/get_collection_releases— curated cross-org "playlists" (e.g. "Frontier AI Labs", "Coding Agents") independent of the category taxonomy.lookup_domain— resolve a URL/domain to the org that owns it. Use when you have a URL-shaped input rather than a name.
The server also exposes signed-in personal-account tools — follow / unfollow / list_follows, get_personalized_feed, and whats_changed (releases since the user's last check across their follows). They require an authenticated connection (OAuth or a user API key) and error for anonymous clients; the reader tools above need no auth. Reach for them only when the user asks about their follows or feed — for general "what's new in X" questions, the reader tools answer without sign-in.
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.
- 9d ago First seen · 74 lines · 64 tokens per session scan A 7f3b1a42aaa6
releases-mcp is a skill published in the GitHub repository buildinternet/releases-cli (4 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 1,471 once invoked, about $0.0003 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
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.sh", "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.