What is releases AGENTS.md?

Repository instructions for Releases, a monorepo—a single repository containing several related applications and services—that stores changelogs and provides an API, web interface, remote MCP server, and managed agents.

Use them when developing, formatting, type-checking, or testing the API, web app, MCP server, database code, or agent harness.

They document the project’s technologies, workspace boundaries, and required checks so changes are made and tested in the correct part of the repository.

releases AGENTS.md — Instructions file by buildinternet

Install

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.

agentmods

npx agentmods add instructions/buildinternet/releases/agents-md

Clone the repo

git clone --depth 1 https://github.com/buildinternet/releases

Made for: Codex, OpenCode.

Per session 11,156 This file is loaded in full into every session.

When invoked 11,156 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.11156	$0.11156
Opus 5	$0.05578	$0.05578
Sonnet 5	$0.02231	$0.02231
Haiku 4.5	$0.01116	$0.01116

Measured 2d ago against content hash e7e3629b6ab0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

releases AGENTS.md 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 2d 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.

AGENTS.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releases

Changelog indexer and registry for AI agents and developers. The user-facing CLI lives out-of-tree at buildinternet/releases-cli; this monorepo is the backend (API worker + D1), the remote MCP server, the web frontend, and the managed-agents harness.

Stack

Runtime: Bun
Language: TypeScript (strict mode)
Database: Cloudflare D1 + Drizzle ORM. No local SQLite path in this repo — bun:sqlite is only used for test fixtures (tests/db-helper.ts).
API: Cloudflare Worker with Hono (workers/api/)
MCP: Remote MCP server (workers/mcp/)
AI: Anthropic SDK (@anthropic-ai/sdk); managed agents via @anthropic-ai/claude-agent-sdk

Commands

Lint + format + type-check: bun run check (oxlint with typeCheck via oxlint-tsgolint, then oxfmt --check)
Lint only: bun run lint (bun run typecheck is an alias)
Format: bun run format:check
Tests: bun test (not part of check)
Targeted tsc: workers/mcp still uses npx tsc --noEmit in CI (carved-out workspace; excluded from root oxlint). web and tests/ have their own tsconfigs for local runs.
Evals (tests/evals/) are manual and on-demand only. They call AI APIs, cost money, and take minutes. bun run eval:evaluation is the only in-repo suite (URL evaluation, ~30s). Parsing + discovery evals live in the OSS CLI repo.

Local development

Running the four dev:* services behind portless, fresh-worktree bootstrap, worktree teardown, and local D1 schema parity (db:reset:local / db:pull) and auth rate-limit / signing-secret notes: local-development.md.

Workspaces and carved-out packages

Root package.json declares workers/api, web, and packages/* as workspaces. workers/discovery/, workers/mcp/, and workers/webhooks/ are intentionally excluded — wrangler manages their dependencies independently.

The root test script runs workers/api in its own bun test process, after the rest: … bun test tests/ web/ workers/discovery workers/mcp workers/webhooks && bun test workers/api. This is deliberate isolation, not a style choice: bun's mock.module() is process-global, keyed by resolved module, and not restorable per-specifier (mock.restore() doesn't undo it, and re-mocking with the real impl is impossible — every import of the path resolves to the mock). The discovery scrape-fetch tests mock.module("@releases/adapters/cloudflare", …) at module scope, and that stub leaks into workers/api's render-check tests, which use the real adapter — an ordering-dependent flake. Splitting workers/api into a separate process makes the leak structurally impossible. Keep discovery (and mcp/webhooks) in the root-cwd multi-dir invocation — that's where their module mocks resolve against the single root-workspace copy of @releases/adapters the source uses. Don't move them to cd workers/discovery && bun test: from a different cwd the test's mock.module and the source resolve @releases/adapters/* inconsistently, so the mock misses and discovery's own tests fail in CI. Isolating workers/api (rather than discovery) is what keeps both sides resolving correctly.

Read the full file on GitHub · 167 lines

Changes

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.

2d ago First seen · 167 lines · 11,156 tokens per session scan A e7e3629b6ab0

Subscribe to this mod's changes

releases AGENTS.md is an instructions file published in the GitHub repository buildinternet/releases (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11,156 tokens to every session, about $0.0558 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.

Git and workflow Releases agent-skills api changelogs mcp registry release notes

ZooData-Skills AGENTS.md

Instructions for SerendipityOneInc/ZooData-Skills, covering repository agent instructions and releasing / publishing.

SerendipityOneInc/ZooData-Skills · 204 tokens

releases-cli AGENTS.md

Instructions for buildinternet/releases-cli, covering agents guide — releases-cli, stack, commands, architecture and conventions.

buildinternet/releases-cli · 5,090 tokens

releases-cli CLAUDE.md

Instructions for buildinternet/releases-cli, a project described as: Agent-friendly CLI for searching the Releases.sh catalog of release notes, changelogs, and product announcements.

buildinternet/releases-cli · 5 tokens

azure-sdk-for-rust changelog.instructions.md

Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.

Azure/azure-sdk-for-rust · 164 tokens

openrouter-mcp-multimodal AGENTS.md

Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).

stabgan/openrouter-mcp-multimodal · 783 tokens

OpenMicro AGENTS.md

Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.

stephenleo/OpenMicro · 123 tokens