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 agentmods add skills/buildinternet/releases-cli/analyzing-releasesnpx skills add buildinternet/releases-cli --skill analyzing-releasesgit 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/analyzing-releases)<a href="https://agentmods.dev/skills/buildinternet/releases-cli/analyzing-releases"><img src="https://agentmods.dev/badge/skills/buildinternet/releases-cli/analyzing-releases.svg" alt="Measured on agentmods" 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.00075 | $0.01227 |
| Opus 5 | $0.00037 | $0.00613 |
| Sonnet 5 | $0.00015 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
analyzing-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 5d 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.
Analyzing Releases
Turn changelog data into competitive intelligence by analyzing release patterns across a cohort of related companies.
This is a reader workflow — it uses only the public, unauthenticated tools. There is no AI summarize/compare tool on the hosted MCP and no summary/compare command in the CLI; you fetch the raw release data and synthesize the analysis yourself.
Tools for each step
| Operation | CLI (reader) | MCP tool |
|---|---|---|
| Find what's indexed for a company | releases search <company> --json |
search (with type: ["orgs","catalog"]) |
| List a company's sources | releases list --query <company> --json |
list_catalog (scope with organization) |
| Latest releases (source or org) | releases tail <slug> --json · releases tail --org <org> --json |
get_latest_releases (organization / product, since/until) |
| Keyword/semantic release search | releases search <query> --json |
search with type: ["releases"] |
| Read one release in full | releases get <rel_id> --json |
get_release |
| Read a tracked CHANGELOG slice | releases admin source changelog <slug> --tokens <n> (key-gated; readers use MCP) |
get_catalog_entry with changelog_tokens / changelog_offset (keyless) |
All releases are indexed already — you don't need to (and as a reader can't) trigger fetches. If a company isn't in the registry at all, say so rather than trying to onboard it; onboarding is an operator task.
Workflow
1. Define the cohort
Pick 3-6 companies in the same competitive space. Good cohorts share a common buyer or technical layer (e.g., developer databases, frontend frameworks, observability tools).
2. See what's indexed
Resolve each company with search (or releases search). For discovery-style cohorts ("find observability vendors with edge offerings"), search with type: ["orgs","catalog"] is vector-backed and matches on description and category — better than a slug-substring list_catalog --query. If a company isn't found, note it as a gap rather than fabricating data.
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.
- 5d ago First seen · 74 lines · 75 tokens per session scan A eec73687fd75
analyzing-releases is a skill published in the GitHub repository buildinternet/releases-cli (4 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 1,227 once invoked, about $0.0004 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
managing-sources
How to create, delete, list, validate, and manage changelog sources — covers ignored/blocked URLs, duplicate detection, and the validation workflow.
maintaining-orgs
Routine maintenance of indexed organizations — fetch all sources, regenerate overviews, verify data quality. Use when asked to "update", "refresh", or "maintain" one or more orgs, or when doing periodic sweeps of the registry.
regenerating-overviews
Generate or refresh an org's AI overview from recent releases. Use when asked to "regenerate", "rewrite", or "refresh the overview" for one or more orgs, or as the regen step inside a maintaining-orgs run.
finding-changelogs
How to find, evaluate, and recommend the best ingestion method for changelog URLs — covers feed discovery, provider detection, GitHub API, markdown sources, and scraping fallback.
local-ingest
Onboard or backfill a company's changelog locally in Claude Code by fetching pages and extracting releases with the agent itself (and parallel sub-agents), then writing through the batch-upsert endpoint — no remote fetch dispatch, no server-side extraction inference billing. Use when you want to onboard a source…
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.