Notification

Notification is a hook for coding agents from AttendantLion8/provider-fallback-plugin. Its token cost is not measured, scanned A, original, MIT.

An automatic hook that runs a Node.js script when the agent receives rate-limit, quota, limit-exceeded, or HTTP 429 notifications.

In plain words
What is it for?
Use it to trigger the specified limit-handling script in response to those usage-limit notifications.
Why use it?
It lets a script respond immediately when a provider or tool reports that usage is temporarily or permanently restricted.

Hook

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

One of 2 entries in hooks.json — they are configured in one file and arrive together.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

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 Notification

README.md
[![agentmods](https://agentmods.dev/badge/hooks/attendantlion8/provider-fallback-plugin/notification.svg)](https://agentmods.dev/hooks/attendantlion8/provider-fallback-plugin/notification)
Your own site
<a href="https://agentmods.dev/hooks/attendantlion8/provider-fallback-plugin/notification"><img src="https://agentmods.dev/badge/hooks/attendantlion8/provider-fallback-plugin/notification.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

Notification 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 3d ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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.

hooks/hooks.json · 10 lines

What it actually says

{
  "Notification": [
    {
      "type": "command",
      "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/handle-limit.js",
      "matcher": "rate_limit|quota|limit exceeded|429",
      "timeout": 5000
    }
  ]
}
Same file

What else hooks.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

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. 3d ago First seen · 10 lines scan A 99b584eb3b33

Subscribe to this mod's changes

Notification is a hook published in the GitHub repository AttendantLion8/provider-fallback-plugin (2 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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.