merge-notify

merge-notify is an agent for coding agents from watt-mind/factory. It costs 0 tokens per session (331 once invoked), scanned A, original, Apache-2.0.

A fixed command that sends an operator notification when a merge-scan check says a pull request needs human review because it changes security-related behavior.

In plain words
What is it for?
Use it after merge scanning to notify an operator that a pull request must be reviewed before it is merged.
Why use it?
It separates urgent security decisions from routine development updates and sends the required escalation message consistently.

Agent

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 agents/watt-mind/factory/merge-notify
Clone the repo
git clone --depth 1 https://github.com/watt-mind/factory

Wrote 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.

agentmods badge for merge-notify

README.md
[![agentmods](https://agentmods.dev/badge/agents/watt-mind/factory/merge-notify.svg)](https://agentmods.dev/agents/watt-mind/factory/merge-notify)
Your own site
<a href="https://agentmods.dev/agents/watt-mind/factory/merge-notify"><img src="https://agentmods.dev/badge/agents/watt-mind/factory/merge-notify.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 331 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00331
Opus 5 $0.00000 $0.00166
Sonnet 5 $0.00000 $0.00066
Haiku 4.5 $0.00000 $0.00033

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

Security

Grade A, and why

merge-notify 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 4d 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.

event-runtime/agents/merge-notify.md · 47 lines

What it actually says

merge-notify — closed-registry action

Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.

factory notify "ESCALATED merge {repo}: {summary}"

Pushes the operator notification for an ESCALATE recommendation from merge-scan@1 — a PR whose diff changes security-relevant behavior (or matches escalate_paths) needs the human decision, per the notification protocol (escalations only, never routine progress). Same shape as ci-notify@1 for ci-doctor@2's TICKET verdict.

Result envelope

The deterministic command adapter, not this command, writes the completed factory.agent-result/v1 wrapper. Its artifact is the factory.command-result/v1 value validated by this definition's registered output schema:

{
  "schemaVersion": "factory.agent-result/v1",
  "terminalState": "completed",
  "reasonCode": "ok",
  "artifact": {
    "command": [
      "factory",
      "notify",
      "ESCALATED merge factory: PR needs a human decision"
    ],
    "exitCode": 0,
    "outputTail": "Notification sent."
  },
  "evidence": {
    "command": [
      "factory",
      "notify",
      "ESCALATED merge factory: PR needs a human decision"
    ],
    "outputTail": "Notification sent."
  }
}
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.

  1. 4d ago First seen · 47 lines · 0 tokens per session scan A 90b186eb0ab0

Subscribe to this mod's changes

merge-notify is an agent published in the GitHub repository watt-mind/factory (12 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 331 tokens. 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.