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.
git 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/plugins/buildinternet/releases-cli/releases)<a href="https://agentmods.dev/plugins/buildinternet/releases-cli/releases"><img src="https://agentmods.dev/badge/plugins/buildinternet/releases-cli/releases/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/plugins/buildinternet/releases-cli/releases"><img src="https://agentmods.dev/badge/plugins/buildinternet/releases-cli/releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
releases 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 11d 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
{
"name": "releases",
"displayName": "Release Notes Index",
"description": "Search changelogs and look up releases via the hosted Release Notes Index. Bundles the hosted MCP connection, the /releases lookup command, and auto-triggering skills for release/changelog questions.",
"author": {
"name": "Build Internet",
"url": "https://github.com/buildinternet"
},
"homepage": "https://releases.sh",
"documentationUrl": "https://releases.sh/docs",
"supportUrl": "https://github.com/buildinternet/releases-cli/issues",
"privacyPolicyUrl": "https://releases.sh/privacy",
"termsOfServiceUrl": "https://releases.sh/terms",
"repository": "https://github.com/buildinternet/releases-cli",
"license": "MIT",
"keywords": [
"changelog",
"release-notes",
"releases",
"version-updates",
"breaking-changes",
"mcp"
]
}
What it installs
The manifest is a name and a version. 3 skills, 1 command, 1 MCP server travel with it, and installing the plugin installs all of them — 245 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 11d ago Changed 4a1bc260f98d
- 16d ago Changed b26e26ffeba7
- 24d ago Changed · +9 lines 62b2f5f7839d
- 25d ago Changed · -1 lines f86ffe5914e0
- 1mo ago First seen · 17 lines scan A a866da9ad31c
releases is a plugin published in the GitHub repository buildinternet/releases-cli (4 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
registry-maintenance
Operator skills for maintaining the registry — ingest, backfills, overviews, release content, playbooks, coverage. Most need an admin API key.
onboarding-parsing
Managed-agent skills for onboarding changelog sources and driving the fetch/parse pipeline.
workflow
Git and GitHub workflow skills — commits, branches, pull requests, issues, and CI actions.
release-runbook
Universal release workflow: detect project type, init versioning, run tests, bump version, tag, push, and create GitHub release.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.