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/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/commands/buildinternet/releases/releases)<a href="https://agentmods.dev/commands/buildinternet/releases/releases"><img src="https://agentmods.dev/badge/commands/buildinternet/releases/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/commands/buildinternet/releases/releases"><img src="https://agentmods.dev/badge/commands/buildinternet/releases/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.00008 | $0.00284 |
| Opus 5.5 | $0.00003 | $0.00114 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- releases — 94% identical, 0 lines differ
What it actually says
/releases
Search changelogs and release notes from the Release Notes Index.
Usage
/releases <product> [query]
/releases --compare <product1> <product2>
- product: A product name, org name, or slug (e.g., "next.js", "tailwind", "vercel")
- query: What you're looking for (optional but recommended for targeted results)
- --compare: Compare recent release activity between two products
Examples
/releases next.js
/releases tailwind v4 breaking changes
/releases prisma migration guide
/releases --compare bun deno
/releases vercel last 7 days
How It Works
- Searches
list_organizationsto resolve the product name to a known org or product - If a query is provided, uses
searchwithtype: ["releases"]filtered to that org - If no query, uses
get_latest_releasesto show the most recent entries - With
--compare, usesget_latest_releaseson both product slugs and synthesizes the comparison - Results include version numbers, dates, and key changes from release notes
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 First seen · 38 lines · 8 tokens per session scan A 3472affb5e27
releases is a command published in the GitHub repository buildinternet/releases (9 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 284 once invoked, about $0.0000 per session on Opus 5.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-10-09.
Other commands, from other repositories
releases
Look up changelogs and release notes.
dev
Dev stage — api-platform-implementer reads .claude/last-api-plan.md and implements (writes code, runs phpstan + phpunit + Infection on critical classes).
symfony-api-errors
Design API Platform 4.3 error handling — RFC 7807.
symfony-api-mcp
Expose API Platform 4.3 operations as MCP tools for AI agents (@experimental).
symfony-migrations
Create and manage Doctrine migrations for database schema changes.
checklist
Generate a custom checklist for the current feature based on user requirements.