Engineering

Check the models in your code every month

Every month, Merlin checks each model id in your code against OpenRouter. You get expiring models and price changes in Slack, and a pull request that moves off anything expiring.

@Merlin on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.

#eng
Get started for free
  1. Starts whenOn the 1st of every month at 10:00, a monthly Merlin schedule posts to #eng
  2. Merlin worksClaude Code or Codex lists every model id in acme/app and checks each in OpenRouter's public models list for an expiration date and a price change since last month
  3. You getThe models expiring or changing price in #eng, with a pull request that replaces each expiring one

Tools

  • Slack
  • OpenRouter
  • GitHub

Capabilities

  • Automations
  • Integrations

How it works

From the model ids in your code to a pull request off the expiring ones.

On the 1st of every month at 10:00, the automation you created from #eng starts a run.

/AcmeTeam/Automations/Check the models in our codeFeedback?O

Overview

Agents

Skills

Memory

Automations

Integrations

Settings

Check the models in our code

Pause
StatusActive
CreatorO Omar You
ScopeWorkspace
Last runOct 1, 2026, 10:00 AM

DetailsRun history

Trigger

When Merlin runs it.

RuleHow often Merlin runs it.Monthly
Day of monthShort months use their final day.1
TimeNext run Nov 1, 2026, 10:00 AM.10:00

Run

What Merlin does each time, where it runs, and where the result goes.

Run instruction

on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.

RuntimeThe computer and coding agent that run it.Omar's MacBook Pro · Claude Code
DestinationWhere Merlin posts the result. Choose None when the instruction already acts in your tools.#eng

Before and after

Expiring models get replaced before they go, not after calls start failing.

Without Merlin

Someone remembers to audit the model ids now and then, looks each one up and makes the swap by hand.

  1. 01Search the code for model ids
  2. 02Look up each model
  3. 03Check for an expiration date
  4. 04Compare prices with last month
  5. 05Pick a replacement
  6. 06Change the model id
  7. 07Run the tests
  8. 08Open a pull request
  9. 09Post the findings in #eng

With Merlin

A monthly schedule catches expiring models early, and a person reviews the move.

  1. Day 1 of every month at 10:00Monthly Merlin schedule in #eng
  2. Checks each model id on Omar's MacBookOpenRouter and the code
  3. Pull request for expiring modelsLinked in #eng with any price changes

Setup

Give your agent OpenRouter and the code, then schedule the check from #eng.

Set these up once and the check runs on the 1st of every month. Merlin never merges, so a person reviews every model change.

  1. 01Connect a machineRuntimeInstall the Merlin desktop app or CLI on a computer running Claude Code or Codex. You can also use a machine a teammate shares with your workspace.
  2. 02Add Merlin to SlackIntegrationsInstall the Slack app and add Merlin to the channel you work in. A private channel needs /invite @Merlin.
  3. 03Keep OpenRouter on your agentOptionalYour agent's MCPIf your machine's agent already uses the OpenRouter MCP server, Merlin can use it here too. You don't need to set up anything in Merlin.
  4. 04Install the GitHub appIntegrationsPick the repositories Merlin can access, so it can read and link the pull requests there. Pushes use the machine owner's own Git access.
  5. 05Keep your code on the machineRuntimeMerlin reads the code in a local project on the runtime, so keep the repository checked out there.
  6. 06Send the prompt from the machine with the codeRuntime

    Runs prefer the machine recorded when the automation is created (choose a runtime), so send it from the one with acme/app checked out. Merlin keeps each month's prices in a local project there, and the first run posts the current prices as the starting point.

  7. 07No OpenRouter key neededYour agent's MCP

    The run reads OpenRouter's public models list, which has every model's price and expiration date, so it doesn't depend on the 7-day key OpenRouter's MCP server mints.

  8. 08Paste the setup promptAutomationsSend the prompt below to @Merlin in Slack, in the channel it should post to. Merlin creates the automation and tells you what it set up.

Prompt

Schedule the monthly model check with one message in #eng.

@Merlin on the 1st of every month at 10:00, list every OpenRouter model id in acme/app and look each one up in OpenRouter's public models list. Post here the ones that have an expiration date or are no longer listed, and any whose price changed since last month (keep each month's prices in the model-prices project on your machine). For each expiring model, open a pull request in acme/app that moves it to the closest current model from the same author and runs the tests. Don't merge it: a person reviews it. If you can't reach OpenRouter, say so.

#eng

Once, when you send it

  1. PromptYou send the prompt to @Merlin
  2. AutomationMerlin creates the automation

Every scheduled run

  1. ScheduleThe schedule starts a run
  2. RuntimeMerlin picks the creator's machine first
  3. ContextThe run gathers context
  4. WorkClaude Code or Codex checks each model in OpenRouter
  5. ResultMerlin posts what changed and links the pull request
  6. SteeringReplies in its thread follow up

Bring your coding agents into the tools your team already uses.

Let your whole team hand work to Claude Code and Codex today. Connect one machine and add Merlin to Slack, Linear or GitHub. 14-day free trial, no API keys, no card.