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 --skill grouping-releasesgit clone --depth 1 https://github.com/buildinternet/releasesWrote 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/grouping-releases)<a href="https://agentmods.dev/skills/buildinternet/releases/grouping-releases"><img src="https://agentmods.dev/badge/skills/buildinternet/releases/grouping-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/skills/buildinternet/releases/grouping-releases"><img src="https://agentmods.dev/badge/skills/buildinternet/releases/grouping-releases.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.00091 | $0.01739 |
| Opus 5 | $0.00046 | $0.00870 |
| Sonnet 5 | $0.00018 | $0.00348 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
grouping-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 10d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grouping Releases
What this is for
Releases enter the index from sources — individual URLs we track for an organization. One org typically has several sources: a product changelog, a news page, an engineering blog, a GitHub repo. When a big launch happens, it's common for multiple sources to cover the same event. A model launch might show up on a marketing post, a platform changelog, and an app-level version note — three releases, one story.
That overlap is signal, not a bug. Readers want the clearest explanation first, with the corroborating entries attached as supporting coverage. This skill decides which releases belong together and which one leads.
When this skill runs
Not at ingest. Ingest-time grouping is deterministic code — the changesets clusterer (clusterAndPersistCascades, decided_by = "system:changesets") links version-cascade coverage automatically as releases land. This skill is the operator lane for the judgment calls that code can't make:
- Batch reconciliation. Reviewing a window of an org's recent releases (e.g.
releases tail --org <org> --json) and deciding the full grouping — typically after a big launch scattered coverage across a marketing post, a changelog entry, and an app note. - Fixing a bad grouping. Unlinking a wrong cluster or re-pointing the canonical.
Scope the candidate set explicitly before judging (an org + a date window). Do not go looking beyond it.
Persisting decisions
- Link:
POST /v1/releases/:canonicalId/coveragewith{ "coverageIds": ["rel_…"], "reason": "…", "decidedBy": "…" }.decidedByMUST be prefixedhuman:oragent:(e.g.agent:claude-code) — the audit trail records who linked the rows. A release cannot be coverage of itself. - Unlink:
DELETE /v1/releases/:id/coverage(idempotent — returns{ unlinked: false }if the release wasn't in a cluster). - Read a cluster:
GET /v1/releases/:id/coverage.
Manual links are durable: the automatic retier only touches decided_by = "system:changesets" rows, so it never clobbers a human/agent decision.
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.
- 10d ago First seen · 100 lines · 91 tokens per session scan A 4cafa8c7c129
grouping-releases is a skill published in the GitHub repository buildinternet/releases (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 91 tokens to every session and 1,739 once invoked, about $0.0005 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
releases-cli
Use the releases CLI to search, browse, and read the Releases.sh changelog registry from the terminal — the keyless, agent-friendly peer of the Releases MCP. Activate when the user mentions "releases CLI", runs a releases command, asks how to install it, or wants to look up releases, sources, orgs, collections, or…
releases-mcp
Use when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".
changelog-generator
Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured .git-log.txt dump). Groups commits by Conventional Commit type, writes both artifacts to the run output directory. Use when asked to draft release notes, summarize commits between tags, or produce a human-readable…
release-checklist
Walk the release checklist before tagging and publishing a version.
changelog-generator
Transform technical git commits into polished, user-friendly changelogs and release notes. Automatically categorizes changes, translates developer language into customer-friendly copy, and generates professional changelog entries.
release-readiness
Use this skill when preparing a tag, package, deployment, or public release.